This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
HTML-standard should define the Context Menu API for browsers. The absence of this API inhibits the development of canvas- or svg-applications. Is the Context Menu an attribute of canvas tag? No. One html-document can encapsulate multiple instances canvas-application (there is no sense to make copies of the context menu). Is the Context Menu an attribute of html-document? No. On one web-site may be published, many html-document included various instances of a canvas-application (does not make sense to create a copy of the context menu in different documents). Is the Context Menu an attribute of web-site or canvas-app? No. Everyone can be a webmaster or designer canvas-application, and the design of the Context Menu should be a single. Summary. Context Menu - is the attribute of the operating system. For Web applications, Context Menu API should provide browser. Is it possible to encapsulate the data to create a context menu in html-document? No. These data are designed for the browser, not for search engines. Is it permissible to create a Context Menu by javascript-code? Yes. Is it permissible to create a Context Menu by data-protocol (url ('data: text / xml; base64, ...'))? Yes. Is it permissible to connect the Context Menu by means of meta-tag? Yes. Does it make sense to transfer in the data to create a Context Menu names of javascript-function? No - only identifiers. -- Sincerely, Klinachev Nikolay Vasilevich
Sounds like an interesting feature to discuss. Setting it to HTML.next as it also sounds like more than we can do for CR.
Mass move to "HTML WG"
See the example for this topic (see URL). -- Sincerely, Klinachev Nikolay Vasilevich
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Additional Information Needed Change Description: none yet Rationale: Is this not addressed by this: http://www.w3.org/html/wg/drafts/html/master/interactive-elements.html#context-menus ? If not, please let us know what is missing.
The fragment of a standard that you have specified was developed in haste. The reason (mistake) mentioned in my first post (the Context Menu is not an attribute of html-document's). Standard should define the JSON-object and browser's Context Menu API. The first step - the data that is specific by the fragment standard should be restructuring from markup by tags to the JSON-object.