Create an example Lit based button component
Categories
(Toolkit :: UI Widgets, task)
Tracking
()
People
(Reporter: hjones, Assigned: hjones)
References
Details
Attachments
(1 obsolete file)
As specified in the reusable components proposal, one of the first components we want to tackle is a Lit based button. We have a complete design spec for this, and it should be relatively straightforward using mostly existing button styles.
Once the Lit vendoring is in place I'll make a first pass at writing a new button component. At the very least this will give us an opportunity to test aspects of the plan laid out in that proposal, and will give us something more concrete to discuss when we're thinking about how to move the reusable components project forward.
Assignee | ||
Comment 1•2 years ago
|
||
Depends on D157473
Updated•2 years ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Just a random question: has anyone done any performance profiling on this kinds of UI widgets?
I'm mostly worried that this doesn't end up using the prototype cache, and thus any page load (UI load) becomes slower.
But perhaps I'm missing something obvious.
Comment 4•1 year ago
|
||
(In reply to Olli Pettay [:smaug][bugs@pettay.fi] from comment #3)
Just a random question: has anyone done any performance profiling on this kinds of UI widgets?
I'm mostly worried that this doesn't end up using the prototype cache, and thus any page load (UI load) becomes slower.
But perhaps I'm missing something obvious.
I've been advocating for using plain button elements with classes for different variants such as "primary", sort what we already do today. IMHO the current wip patch is an unnecessarily convoluted abstraction in search for a real purpose that would justify introducing a custom element here.
Assignee | ||
Comment 5•7 months ago
|
||
This is no longer relevant now that the work of creating a button component is happening on Bug 1791816
Updated•7 months ago
|
Description
•