- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 May 2013 18:07:19 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22022 Bug ID: 22022 Summary: RegisterProtocolHandler needs to accept http POST request, if possible Classification: Unclassified Product: HTML WG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec Assignee: dave.null@w3.org Reporter: follybeachris@hotmail.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org I recently experienced the benefit that HTML5 RegisterProtocolHandler seems to afford users by making use of the "ExportTabs" utility offered to browser-users employing Chrome as their web-tool of choice - and while elated- was equally taken back by the potential drawback that is HTML5/RegisterProtocolHandler/GMail/mailto's inability to parse/handle my POST request to construct an email. I would like to see future spec(s) embrace or enhance this feature-request so as to avoid a cap on the message-body length as is currently being posed by mailto: transforming requests via (I presume) HTTP GET query transformation. IOW, if the ExportTabs browser-extension works in conjunction with the RegisterProtocolHandler() implementation via taking the browser-user's open tabs and converting them (to include various html attributes) to a "mailto:user?body=<http GET request>",then a "mailto:user?body=<POST request>" capability would resolve my concern. I have not contacted the developer as to how their extension works, nor have I TBH conducted suitable research, but to those concerned, your great and attention to this work is indeed very appreciated!! Thank you for your commitment to open web'ed-ness. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 13 May 2013 18:07:21 UTC