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 11450 - Reconsider <img src=""> with a base URL
Summary: Reconsider <img src=""> with a base URL
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: 2010-12-01 20:12 UTC by contributor
Modified: 2011-08-04 05:11 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2010-12-01 20:12:04 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#update-the-image-data

Comment:
Reconsider <img src=""> with a base URL

Posted from: 91.181.100.3 by ms2ger@gmail.com
Comment 1 Ms2ger 2010-12-01 20:13:20 UTC
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/724

IE: fires error
Chrome/Gecko: fires load
Opera: doesn't fire anything
Comment 2 Jonas Sicking (Not reading bugmail) 2010-12-01 20:18:14 UTC
If the semantic meaning of <img src=""> is "no image here, don't load anything", then Opera's behavior makes the most sense to me.
Comment 3 Simon Pieters 2010-12-01 21:05:34 UTC
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-December/024613.html shows two pages that expect an error event for <img src="">.
Comment 4 Ms2ger 2010-12-02 08:14:54 UTC
I don't want to reopen the discussion about <img src=""> in general; just for the specific case where the img has another base URL than the page itself.

For reference:
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-March/025507.html
http://html5.org/tools/web-apps-tracker?from=4840&to=4841
https://bugzilla.mozilla.org/show_bug.cgi?id=599975
Comment 5 Simon Pieters 2010-12-02 10:46:04 UTC
The point of not fetching anything for <img src=""> was to reduce useless fetching. I think most pages that use <base> just use it to point to their site's root for convenience in writing their <a href>s, and don't expect it to make their <img src=""> templates suddenly make network requests.
Comment 6 Jonas Sicking (Not reading bugmail) 2010-12-02 18:38:27 UTC
Indeed. I don't think the base URL should affect anything here. Neither what requests hit the network, nor what events are fired.

(Note that I think firefox doesn't behave like what I just described, but I think we should change that)
Comment 7 Ian 'Hixie' Hickson 2010-12-08 00:14:56 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: Spec fires 'error'. I don't think there's much point supporting src="" with a base URL, for the reason given in comment 5.
Comment 8 Jonas Sicking (Not reading bugmail) 2010-12-08 00:44:16 UTC
I filed bug comment 2
Comment 9 Jonas Sicking (Not reading bugmail) 2010-12-08 00:44:57 UTC
I filed bug 11497 on comment 2
Comment 10 Michael[tm] Smith 2011-08-04 05:11:40 UTC
mass-move component to LC1