Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limitations of this approach #4

Open
limefrogyank opened this issue May 19, 2019 · 1 comment
Open

Limitations of this approach #4

limefrogyank opened this issue May 19, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@limefrogyank
Copy link

After playing around with your port of Fabric, I'm having trouble getting around one big problem with server-side blazor.

With server-side Blazor, you currently have to wait until after the first render for javascript interop to be available. As this library depends heavily on javascript since we are adding stylesheets via `, all of the controls show up in their unstyled state for a small amount of time before being transformed to their Fabric styles. It's pretty ugly.

It seems it might be a good idea to go without Javascript (as much as possible). I've tried an approach where I create a FabricStyle component that you stick somewhere near the root component. All it does is contain a <style></style> tag and watches an IObservable that outputs the latest set of css rules. It seems to work ok.

I don't have a solution for RTL or browser-specific prefixes yet though.

@galvesribeiro
Copy link
Member

Good idea. I'm out on vacation returning by the end of the month. Please expect an update on that earlier next month.

@galvesribeiro galvesribeiro added the enhancement New feature or request label May 20, 2019
@galvesribeiro galvesribeiro self-assigned this May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants