- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Dec 2012 16:50:41 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20239 Bug ID: 20239 Summary: Context Menu API for browsers (4 canvas-app) Classification: Unclassified Product: HTML WG Version: unspecified Hardware: PC OS: Windows XP Status: NEW Severity: normal Priority: P2 Component: HTML Canvas 2D Context Assignee: jaymunro@microsoft.com Reporter: klinacherv_nv@mail.ru QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org 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 -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 4 December 2012 16:50:50 UTC