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 16899 - This is a suggestion: If HTML5 would contain resource pool in each browser. i.e. all HTML5 supporting browsers would have a collection of icon set for example: someone may use them like this: <img src='chrome:://html5/res/images/alarm.png' width='512' he
Summary: This is a suggestion: If HTML5 would contain resource pool in each browser. i...
Status: RESOLVED LATER
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-01 18:10 UTC by contributor
Modified: 2012-09-14 12:12 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2012-05-01 18:10:14 UTC
Specification: http://dev.w3.org/html5/spec/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
This is a suggestion:

If HTML5 would contain resource pool in each browser.

i.e. all HTML5 supporting browsers would have a collection of icon set

for example: someone may use them like this: 

<img src='chrome:://html5/res/images/alarm.png' width='512' height='512' />

OR audio set

<audio controls="controls">
  <source src="chrome:://html5/res/audio/beep.mp4" type="audio/mpeg" />
  Your browser does not support the audio element.
</audio>

Which will decrease the downloadable content and give the developers a set of
resources to use.

Posted from: 41.235.56.119
User agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20100101 Firefox/13.0
Comment 1 contributor 2012-07-18 07:21:01 UTC
This bug was cloned to create bug 17942 as part of operation convergence.
Comment 2 Edward O'Connor 2012-08-21 21:12:27 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: While it may be worth trying to design such a feature for
HTML.next, I don't think we should attempt to do so in the HTML5
timeframe.