[Bug 11497] New: Don't fire an "error" event for <img src="">

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11497

           Summary: Don't fire an "error" event for <img src="">
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#upd
                    ate-the-image-data
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: jonas@sicking.cc
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, jonas@sicking.cc,
                    contributor@whatwg.org, Ms2ger@gmail.com


+++ This bug was initially created as a clone of Bug #11450 +++

The whole reason that we have special handling for <img src="">, rather than
just resolving "" against the current base and attempting to load it, is that
it is apparently quite common for sites to do:

<img src="<?php echo $top_banner;?>">

where sometimes people forget to set, or opt not to set, $top_banner.

In this case it doesn't make sense to fire an "error" event since no load
actually failed.

Instead I propose we change step 5 to say:

"If the element's src attribute's value is the empty string, then set the
element to the unavailable state and abort these steps.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 8 December 2010 00:43:37 UTC