[Bug 13344] Attributes to tags for Dynamic Update:

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13344

Erika Doyle Navara <erika.doyle@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |erika.doyle@microsoft.com
         Resolution|---                         |WONTFIX

--- Comment #3 from Erika Doyle Navara <erika.doyle@microsoft.com> ---
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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 15 February 2013 00:14:13 UTC