[Bug 25358] "Context info: UIEvent.view" sometimes only has defaultView

[email protected]
Newsgroups gmane.comp.web.dom.general
Message-ID <[email protected]/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25358

Gary Kacmarcik <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Gary Kacmarcik <[email protected]> ---
https://dvcs.w3.org/hg/dom3events/rev/40019b0b87c3

(In reply to spiritRKS1910 from comment #7)
> (In reply to Gary Kacmarcik from comment #5)
> 
> In free time I can collect all the weird cases in one place (that caught my
> attention), but in reality it would require more work. Something can be add,
> something remove, but perhaps it would be better than the current state of
> these tables.

Travis and I went through these and compared them with HTML5 and updated these
tables. The target types and UIEvent.view context should reflect the trusted
events and should also be consistent between the summary table and the event
tables.

We also updated the tables to be more explicit that they are describing trusted
events (and trusted event context).

If you have a chance to review the information there, that would be great.  We
still have to do a bit more cleanup in other parts of the table to make it
consistent and complete.

> (In reply to Gary Kacmarcik from comment #6)
> 
> >Argh!  I just noticed that the table in 5.1.1 does say "Trusted event target types" at the top of the column.
> 
> That is why I proposed to take into account only trusted cases (Comment 2).
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=25357#c2

I missed that the first time I was looking at the table. Thanks for bringing
that to my attention.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.