-
Notifications
You must be signed in to change notification settings - Fork 947
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
Widget styling #2518
Comments
For images, additionnally to URLs, we could also accept SVG strings and transform them to get the right syntax and optimization .. |
Yes. We've been extending things as users request them.
We used to have arbitrary CSS styling. However, essentially this makes the DOM structure part of the api, and the new styling system is an effort to put a level indirection between styling options and the DOM structure (so we can change the DOM structure now without breaking backwards compatibility). As such, each styling addition creates a maintenance burden on us to maintain. That's why we've been conservative and adding to the styles when there were specific requests for needs people actually had. Note that the Layout provides many styling properties for the top-level DOM element, including borders. The Style system is primarily for styling elements inside the widget. |
Thanks @jasongrout. I'll probably come back later with more precise requirements. |
Sagemath on Jupyter users, and Sage Combinat Widgets/Sage Explorer users, would really like to be able to change display attributes programmatically, the simplest way possible .. like:
|
See also #2611 |
Hi. Do we intend to extend the styling possibilities through the widgets_style.Style?
For instance, we (at sagemath) would like to have:
---- tiny brainstrorming ----
For a button,
background-image
could be calledbutton_image
.background
as such could also exist and be calledbackground
(and not only for buttons).---- end ----
Is there a reason to limit ourselves? Could we not just accept every CSS property when applicable, changing the name only for some of them?
The text was updated successfully, but these errors were encountered: