[Bug 15948] <area> should be classified as "interactive content"

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

steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |faulkner.steve@gmail.com
         Resolution|---                         |WONTFIX
           Assignee|dave.null@w3.org            |faulkner.steve@gmail.com

--- Comment #2 from steve faulkner <faulkner.steve@gmail.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 spec change
Rationale: the intended use of <area> is to confer interactive regions on an
object or img element not for the area element itself to be interactive
content. Although you have shown that through use of CSS gymnastics:

html body map area,
html body map area:link

{
       display:inline-block!important;
         width:150px!important;
    }
   area:before { content:  "Area: " attr(alt); }
   area:link:before { content:  "Area: " attr(alt); }
area:visited:before { content:  "Area: " attr(alt); }
area {cursor:inherit;color:blue;}
* area{background:yellow!important;}
map area{background:orange!important;}
img map area, object map area { background:red!important;}
* img area,* object area { background:lime!important;}

it is possible to make an area element clickable in some browsers, I don't see
the advantage to classifying it as interactive content. It is also possible to
make any element clickable and actionable through the use of tabindex, but
elements are classified according to their indended use. If you have evidence
of a pattern of use for area being used in the wild asyou describe, feel free
to provide such data.

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

Received on Monday, 11 February 2013 10:24:51 UTC