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 28361 - Ambiguity in the context value for content loaded through <meta http-equiv=refresh> in a frame/iframe
Summary: Ambiguity in the context value for content loaded through <meta http-equiv=re...
Status: RESOLVED INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-28 21:16 UTC by Ehsan Akhgari [:ehsan]
Modified: 2015-09-02 09:34 UTC (History)
2 users (show)

See Also:

Attachments

Description Ehsan Akhgari [:ehsan] 2015-03-28 21:16:45 UTC 
It's not clear whether the UA should set the context to "metarefresh" or "frame"/"iframe" in that case.
Comment 1 Anne 2015-03-30 10:04:44 UTC 
I think it should be "metarefresh" but this is really up to the HTML specification to define once it integrates with Fetch.
Comment 2 Ehsan Akhgari [:ehsan] 2015-03-30 15:21:55 UTC 
Moving to HTML then.
Comment 3 Anne 2015-09-02 09:34:52 UTC 
This is no longer a problem since context is gone.