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 13341 - typo in Facebook fix?
Summary: typo in Facebook fix?
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-24 07:55 UTC by contributor
Modified: 2015-01-31 04:42 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2011-07-24 07:55:58 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#navigate-fragid-step
Complete: http://www.whatwg.org/c#navigate-fragid-step

Comment:
typo in Facebook fix?

Posted from: 81.234.240.242
User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.181 Version/12.00
Comment 1 Philip Jägenstedt 2011-07-24 08:09:14 UTC
http://html5.org/r/6322 introduces "if the URL of the target of the redirect does not have a fragment identifier and the URL of the resource that led to the redirect does, then the URL of the resource that led to the redirect must be propagated to the URL of the target of the redirect."

The last two instances of "URL" should be something with fragment identifiers, unless "propagating a URL to a URL" is suitably defined to do that.
Comment 2 Michael[tm] Smith 2011-08-04 05:17:27 UTC
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-15 05:25:31 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: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 4 contributor 2011-08-15 05:26:57 UTC
Checked in as WHATWG revision r6457.
Check-in comment: typo
http://html5.org/tools/web-apps-tracker?from=6456&to=6457