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 12096 - Firefox uses the last meta refresh rather than the first. Test case: http://jsfiddle.net/J58rd/
Summary: Firefox uses the last meta refresh rather than the first. Test case: http://j...
Status: RESOLVED WONTFIX
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-02-16 12:49 UTC by contributor
Modified: 2011-08-04 05:12 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-02-16 12:49:30 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#table-http-equiv

Comment:
Firefox uses the last meta refresh rather than the first. Test case:
http://jsfiddle.net/J58rd/

Posted from: 120.17.215.54
Comment 1 Ian 'Hixie' Hickson 2011-05-04 21:38:52 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: Rejected
Change Description: no spec change
Rationale: Firefox, Opera, and WebKit use the last one when they're all the same. They use the last one with the earliest time if there's several conflicting times. They use different ones if the elements are inserted at different times. Try changing the timing on this one (900, 1100, 2000):

   http://software.hixie.ch/utilities/js/live-dom-viewer/saved/976

IE always goes with the first one, exactly per spec. This is a far simpler solution, and since it's IE doing it, likely not a compat problem. So I think on the whole it would be better to converge on what the spec says now.

If you disagree, please actually describe in detail what the conformance criteria should be, because I can't work out how to phrase the more complicated behaviour such that it handles all the various edge cases.
Comment 2 Michael[tm] Smith 2011-08-04 05:12:20 UTC 
mass-move component to LC1