W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2013

Re: [DOM3 Events] relatedTarget on blur/focus

From: Ojan Vafai <ojan@chromium.org>
Date: Thu, 7 Feb 2013 10:02:15 -0800
Message-ID: <CANMdWTsyt8FoZW48GveTSD6FTgEtuzGJFJ9i=gtL5G63WoY_GA@mail.gmail.com>
To: "www-dom@w3.org" <www-dom@w3.org>
Warnocked!

WebKit just got relatedTarget on focus/blur. I take the silence as there
being no opposition, since there wasn't a clear reason for excluding them
in the first place. Would be great if we could update the spec.


On Wed, Oct 31, 2012 at 2:15 PM, Ojan Vafai <ojan@chromium.org> wrote:

> 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 Thursday, 7 February 2013 18:03:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 February 2013 18:03:17 GMT