<scribe> Scribe: Patrick_H_Lauke

<smaug> in a minute

The behavior of `touch-action: none` on <iframe> is unclear

https://github.com/w3c/pointerevents/issues/325

Patrick: I had an action item to just draft a note
... and so I did https://github.com/w3c/pointerevents/pull/334

if you could have a look to make sure i have the technical terms etc right, if it needs more, etc

Smaug: i think that should be quite ok

Patrick: let's merge it

Olli to file UI events issue for https://github.com/w3c/pointerevents/issues/191

Smaug: I filed, but not heard back. not sure how often they look at UI events issues

Olli to reach out to Bo about the other spec

<smaug> https://github.com/w3c/pointerevents/issues/134#issuecomment-693491382

Smaug: Bo didn't reply yet to this

Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers https://github.com/w3c/pointerevents/issues/285#issuecomment-662547965

action was for Google to review/comment, but no reply there. will need to chase up navid/mustaq a bit more directly

not using <dfn> https://github.com/w3c/pointerevents/issues/333

Patrick: i have no understanding directly of how respec does things, have been cargo-culting respect stuff that i inherited.

Smaug: unfortunately no idea either

Patrick: i might ask PLH or mcaceres for help on that, as i think Anne uses bikeshed so isn't familiar directly with what we need to do

Click event while a pointer event is captured https://github.com/w3c/pointerevents/issues/75

Smaug: not worked on this.

Patrick: as long as we don't lose track of it

* Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers https://github.com/w3c/pointerevents/issues/285#issuecomment-662547965

Patrick: sorry that's the UI event one

Smaug: need to hear back from Navid on this, whether it's ok to change the behaviour

<scribe> ACTION: reach out to Navid/Mustaq about this issue for comment

touch-action and scrolling directional lock https://github.com/w3c/pointerevents/issues/303

Patrick: similar to the note i added, this seems to be that it's behaviour implied by our spec, but not made obvious. would need at least a note clarifying this. will look into this

<scribe> ACTION: Patrick to look at note for issue 303

still have hanging PR https://github.com/w3c/pointerevents/pull/317

Patrick: think we're still waiting to see what the decision/outcome is https://github.com/whatwg/html/pull/5324

Navid looked at this two weeks ago, think some WPTs need to be added. we'll wait until that issue is closed/resolved before merging our PR

Some tests don't work properly with mobile-sized viewports

https://github.com/w3c/pointerevents/issues/139

Patrick: might be outdated and irrelevant...or not

navid is assigned, so might prod him again about this

<scribe> ACTION: Patrick to prod Navid about issue 139

Patrick: so, as it's just the two of us, think we can cut this meeting a bit shorter, no point in opening up any new issues to look at

Smaug: sure, but will you reach out to Navid/Google

Patrick: yes, will send email in next half hour or so while it's fresh in my mind. In meantime, thank you, and catch you next time again.

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Patrick_H_lauke smaug

WARNING: Fewer than 3 people found for Present list!

Found Scribe: Patrick_H_Lauke
Inferring ScribeNick: Patrick_H_Lauke
Agenda: https://lists.w3.org/Archives/Public/public-pointer-events/2020JulSep/0085.html

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: out patrick reach

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)