Closed
Bug 746087
Opened 12 years ago
Closed 5 years ago
Implement HTML5 toolbar menus
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: janv, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tw-dom])
Attachments
(3 files)
215.26 KB,
image/png
|
Details | |
205.96 KB,
image/png
|
Details | |
20.97 KB,
patch
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → Jan.Varga
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•12 years ago
|
||
Should this implementation follow the proposal at https://www.w3.org/Bugs/Public/show_bug.cgi?id=13608#c6 ? So the syntax would be: <toolbar> <toolbarbutton> <toolbarbutton> ... </toolbar>
Comment 2•12 years ago
|
||
Adding yet another random unspec'ed tag? Browser wars came again!
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #2) > Adding yet another random unspec'ed tag? Browser wars came again! No, we're going to discuss about it first
Reporter | ||
Comment 4•12 years ago
|
||
anyway, the <menuitem> is not in the standard :)
Comment 5•12 years ago
|
||
(In reply to Jan Varga [:janv] from comment #3) > (In reply to Masatoshi Kimura [:emk] from comment #2) > > Adding yet another random unspec'ed tag? Browser wars came again! > No, we're going to discuss about it first And it appears that a spec editor oppose adding <menuitem>. Moreover, the spec bug was filed after Henri pointed out in bug 676236 comment #2. (In reply to Jan Varga [:janv] from comment #4) > anyway, the <menuitem> is not in the standard :) Then making things even worse?
Comment 6•12 years ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #5) > And it appears that a spec editor oppose adding <menuitem>. So? If the spec is bad, it should be changed.
Reporter | ||
Comment 7•12 years ago
|
||
here's an old screenshot, will attach a new one and also a WIP patch
Reporter | ||
Comment 8•12 years ago
|
||
Reporter | ||
Comment 9•12 years ago
|
||
Blocks: html5test
Comment 10•10 years ago
|
||
The spec changes a little bit, menuitem is back I guess. menu[type="context"] is now menu[type="popup"] same for <menu>
Flags: needinfo?(Jan.Varga)
Reporter | ||
Comment 12•10 years ago
|
||
Yeah, the spec has changed (mostly the way we wanted), but unfortunately updating our implementation is not a priority at the moment :(
Flags: needinfo?(Jan.Varga)
Updated•10 years ago
|
Keywords: dev-doc-needed
Comment 13•8 years ago
|
||
Jan, any chance you can resume development on this bug? This has gotten much more relevant, especially in the light of XUL deprecation, and it'll allow many parts of the UI to be rewritten in HTML (Developer Tools for example).
Flags: needinfo?(jvarga)
Reporter | ||
Comment 14•8 years ago
|
||
(In reply to Tim Nguyen [:ntim] from comment #13) > Jan, any chance you can resume development on this bug? This has gotten much > more relevant, especially in the light of XUL deprecation, and it'll allow > many parts of the UI to be rewritten in HTML (Developer Tools for example). I don't have the time currently, but maybe someone else from the DOM team could take it.
Flags: needinfo?(jvarga)
Updated•8 years ago
|
Whiteboard: [tw-dom]
I'm not convinced this bug is worth fixing. At the very least we should check that other browsers are interested before we implement anything. If we end up being the only one implementing, developers are very unlikely to use this.
Comment 16•8 years ago
|
||
(In reply to Jonas Sicking (:sicking) from comment #15) > I'm not convinced this bug is worth fixing. At the very least we should > check that other browsers are interested before we implement anything. If we > end up being the only one implementing, developers are very unlikely to use > this. Sure.
Assignee: jvarga → nobody
Status: ASSIGNED → NEW
Comment 17•8 years ago
|
||
According to http://html5accessibility.com/, we support menuitem, and partially menu popups, and we're the only ones doing so. If we implemented this fully, it would give us an edge and maybe entice others to follow our lead, alleviating the need for ugly hacks web developers need to implement nowadays for such menu systems.
Comment 18•8 years ago
|
||
(In reply to Jonas Sicking (:sicking) from comment #15) > If we > end up being the only one implementing, developers are very unlikely to use > this. If a feature is wanted and its implementation was decent then wouldn't developers prefer to create polyfills, that seems to be less painful than to implement a feature for all browsers from scratch.
Comment 19•8 years ago
|
||
(In reply to Jonas Sicking (:sicking) from comment #15) > I'm not convinced this bug is worth fixing. At the very least we should > check that other browsers are interested before we implement anything. If we > end up being the only one implementing, developers are very unlikely to use > this. If it helps, other browsers are finally stirring on the context menu support that Firefox has had for a while. Chrome's got an implementation of the context menu support but it's being held behind an experimental feature flag because they followed the spec more closely than Firefox, it broke a site, and discussions on changing the spec apparently went nowhere. https://bugs.chromium.org/p/chromium/issues/detail?id=87553 (implementation) https://bugs.chromium.org/p/chromium/issues/detail?id=412945 (site evangelism bug) I don't know how accurate it is, but caniuse.com claims that Opera inherited that ability by their use of Blink: http://caniuse.com/#feat=menu As for Edge, there's a UserVoice request to support it and Microsoft has the feature listed as under consideration (probably because of the aforementioned issue Chrome ran into). https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6508881-html5-menu-tag-contextmenu-attribute https://dev.windows.com/en-us/microsoft-edge/platform/status/menuelement
Updated•6 years ago
|
Priority: -- → P5
Comment 20•5 years ago
|
||
I'm going to close this since this bug is quite confusing. Let's use bug 897102 to align with the standard.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•