W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2012

[Bug 19804] New: relatedTarget on blur/focus should match focusout/focusin

From: <bugzilla@jessica.w3.org>
Date: Wed, 31 Oct 2012 21:14:17 +0000
To: www-dom@w3.org
Message-ID: <bug-19804-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19804

          Priority: P2
            Bug ID: 19804
                CC: mike@w3.org, www-dom@w3.org
          Assignee: schepers@w3.org
           Summary: relatedTarget on blur/focus should match
                    focusout/focusin
        QA Contact: public-webapps-bugzilla@w3.org
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: ojan@chromium.org
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: DOM3 Events
           Product: WebAppsWG

http://lists.w3.org/Archives/Public/www-dom/2012OctDec/0061.html

Right now relatedTarget is specced as being null on blur/focus. Why don't these
just match focusout/focusin?

Doing some spec archaeology, it looks like relatedTarget was specced as having
the same value as target on blur/focus and then set to null in response to
http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0010.html.

It seems to me that there's no downside to making relatedTarget do the same
thing on focus/blur that is does on focusout/focusin respectively. From a web
developers perspective, the only difference should be whether the event bubbles
or not and whether it fires before/after focus has shifted.

I know this is late in the cycle, but I just noticed this and this seems
reasonable to include in the level 3 version of this spec.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 31 October 2012 21:14:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 31 October 2012 21:14:20 GMT