This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13008 - Great feature. I think protocol handler should allow another parameter that is true/false. This would allow a temporary register that would only affect the page it was called from, and only during the lifetime of the page. Also, as a security concern,
Summary: Great feature. I think protocol handler should allow another parameter that ...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-21 13:50 UTC by contributor
Modified: 2011-08-25 22:32 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-06-21 13:50:27 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html
Multipage: http://www.whatwg.org/C#custom-handlers
Complete: http://www.whatwg.org/c#custom-handlers

Comment:
Great feature.	I think protocol handler should allow another parameter that
is true/false.	This would allow a temporary register that would only affect
the page it was called from, and only during the lifetime of the page.	Also,
as a security concern, you wouldn't be able to override known handlers.  All
other security concerns should be addressed with the exception that if its all
temporary,  and same domain policy is in effect, that it would not require the
user to approve of it.

Posted from: 173.62.198.36
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Comment 1 Michael[tm] Smith 2011-08-04 05:06:52 UTC 
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-25 22:32:33 UTC 
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: Did Not Understand Request
Change Description: no spec change
Rationale: What would the use case be? Surely if it's only for the current page, you could just rewrite the links manually to point to the handler.