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 13344 - Attributes to tags for Dynamic Update:
Summary: Attributes to tags for Dynamic Update:
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-24 14:33 UTC by praveen
Modified: 2013-02-15 00:14 UTC (History)
5 users (show)

See Also:


Attachments

Description praveen 2011-07-24 14:33:06 UTC
Option to dynamically update a tag contents for which the refresh period can be given in the same tag.
Comment 1 Robin Berjon 2013-01-21 15:58:33 UTC
Mass move to "HTML WG"
Comment 2 Robin Berjon 2013-01-21 16:01:19 UTC
Mass move to "HTML WG"
Comment 3 Erika Doyle Navara 2013-02-15 00:14:10 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 change
Rationale: 

It sounds like you are asking for a new attribute, e.g., refresh="5s", that would only apply to replaced elements like iframes, since we don't want to allow arbitrary elements to load or replace their content from a URL. The use case sounds like it is for ads, which usually use JavaScript to request and update content from different URLs. Its not very typical to serve multiple unique documents from a single URL, as that would generally make the experience unpredictable. Adding a refresh attribute to an iframe would only request the same content, most likely from the cache, or if not, one would typically expect the same content from the server.

Extrapolating from your idea, it sounds like this could be a request for an iframe source carousel, which is an interesting notion. However, the use cases seem fairly limited at this point.