You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That root class remains in the tree even when you are logged in, which forces the applications layout to deal with being a flex child, and contained in a height:100vh parent element.
The logged in UI should not have to deal with layout choices of the authenticator log in screen. Related to #349
The text was updated successfully, but these errors were encountered:
only include the `w3ui-authenticator` class in the dom when we want to show the log in box.
otherwise the layout we choose for the register form is inherited by the logged in app layout which is undesirable
fixes#351
License: MIT
Signed-off-by: Oli Evans <oli@protocol.ai>
only include the `w3ui-authenticator` class in the dom when we want to
show the log in box.
otherwise the layout we choose for the register form is inherited by the
logged in app layout which is undesirable
fixes#351
License: MIT
Signed-off-by: Oli Evans <oli@protocol.ai>
Peeja
pushed a commit
to storacha/upload-service
that referenced
this issue
Jan 29, 2025
only include the `w3ui-authenticator` class in the dom when we want to
show the log in box.
otherwise the layout we choose for the register form is inherited by the
logged in app layout which is undesirable
fixesstoracha/w3ui#351
License: MIT
Signed-off-by: Oli Evans <oli@protocol.ai>
We're applying a set of style to
.w3ui-authenticator
to allow us to show a full screen "not logged in" contsainer.https://github.com/web3-storage/w3ui/blob/0c661c6f4d28776b4ac7ad1aea3e0958186f8480/packages/react/src/styles/authenticator.css#L22-L28
That root class remains in the tree even when you are logged in, which forces the applications layout to deal with being a flex child, and contained in a height:100vh parent element.
The logged in UI should not have to deal with layout choices of the authenticator log in screen. Related to #349
The text was updated successfully, but these errors were encountered: