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

Re: [DOM3 Events] relatedTarget on blur/focus

From: Ojan Vafai <ojan@chromium.org>
Date: Wed, 31 Oct 2012 14:15:02 -0700
Message-ID: <CANMdWTuf6bcqFEmgCLniQ3f3Fo5GDvW5iYvnrfh35LjaXpQTxQ@mail.gmail.com>
To: "www-dom@w3.org" <www-dom@w3.org>
Went ahead and filed the bug:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19804.


On Tue, Oct 30, 2012 at 1:43 PM, Ojan Vafai <ojan@chromium.org> wrote:

> 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.
>
> Ojan
>
Received on Wednesday, 31 October 2012 21:15:51 GMT

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