Sorry I forgot to reply here! In my opinion this is not something we would want to expose to a DevTools (or test automation end user). I don't think users would benefit from this. Enabling touch simulation should remain a global feature. If we go for 2.A then DevTools would have to emulate the inheritance somehow. I think 2.B can be a good compromise. We will only ever set overrides on the topmost context. So as long as updating the override is properly inherited by descendent contexts which didn't set a specific override this would be ok. Would the following scenario work with 2.B? - assuming two contexts, parent and child - both have initially `touchEventsOverride` set to "none" (default) - start touch simulation, which set `parent.touchEventsOverride = "enabled"` - child should now inherit from this and be "enabled" as well - stop touch simulation, which sets `parent.touchEventsOverride = "none"` - child should also revert back to "none" If this works with 2.B, I think we should be ok. Adding :micah, :bwerth and :rcaliman in cc.
Bug 1677774 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry I forgot to reply here! In my opinion this is not something we would want to expose to a DevTools (or test automation) end user. I don't think users would benefit from this. Enabling touch simulation should remain a global feature. If we go for 2.A then DevTools would have to emulate the inheritance somehow. I think 2.B can be a good compromise. We will only ever set overrides on the topmost context. So as long as updating the override is properly inherited by descendent contexts which didn't set a specific override this would be ok. Would the following scenario work with 2.B? - assuming two contexts, parent and child - both have initially `touchEventsOverride` set to "none" (default) - start touch simulation, which sets `parent.touchEventsOverride = "enabled"` - child should now inherit from this and be "enabled" as well - stop touch simulation, which sets `parent.touchEventsOverride = "none"` - child should also revert back to "none" If this works with 2.B, I think we should be ok. Adding :micah, :bwerth and :rcaliman in cc.