Bugzilla

Closing the duplicates as it spreads the conversion and makes this hard to follow.  

There are still 2 important items to consider here:
- other browsers do not allow to pick element with pointer-events: none
- without a specific UX work around this, simply allowing to pick `pointer-events: none` elements might be more annoying than it is useful (see Bug  745489 comment 3)

I quickly tried `nsDOMWindowUtils.nodesFromRect` and it seems we can use it to pick those nodes, with minimal codechange. However we'd need to perform some more tests to understand in which case this code might start returning unexpected nodes. In general we should be careful if this starts returning invisible nodes. 

So in the end I think that modifying the default behavior of the picker is complicated and probably needs UX work (eg put it behind an explicit user action with some UI?).

However if we want to add this experimental behind a preference so that webcompat team can use it, it can be done pretty easily. I will submit a basic patch doing that. If anyone wants to pick it up, polish it, add tests and try to review the behavior on more examples, I can't imagine this would take more than a few days of implementation + review.

Closing the duplicates as it spreads the conversation and makes this hard to follow.  

There are still 2 important items to consider here:
- other browsers do not allow to pick element with pointer-events: none
- without a specific UX work around this, simply allowing to pick `pointer-events: none` elements might be more annoying than it is useful (see Bug  745489 comment 3)

I quickly tried `nsDOMWindowUtils.nodesFromRect` and it seems we can use it to pick those nodes, with minimal codechange. However we'd need to perform some more tests to understand in which case this code might start returning unexpected nodes. In general we should be careful if this starts returning invisible nodes. 

So in the end I think that modifying the default behavior of the picker is complicated and probably needs UX work (eg put it behind an explicit user action with some UI?).

However if we want to add this experimental behind a preference so that webcompat team can use it, it can be done pretty easily. I will submit a basic patch doing that. If anyone wants to pick it up, polish it, add tests and try to review the behavior on more examples, I can't imagine this would take more than a few days of implementation + review.

Closing the duplicates as it spreads the conversation and makes this hard to follow.  

There are still 2 important items to consider here:
- other browsers do not allow to pick element with pointer-events: none
- without a specific UX work around this, simply allowing to pick `pointer-events: none` elements might be more annoying than it is useful (see Bug  745489 comment 3)

I quickly tried `nsDOMWindowUtils.nodesFromRect` and it seems we can use it to pick those nodes, with minimal codechange. However we'd need to perform some more tests to understand in which case this code might start returning unexpected nodes. In general we should be careful if this starts returning invisible nodes. 

So in the end I think that modifying the default behavior of the picker is complicated and probably needs UX work (eg put it behind an explicit user action with some UI?).

However if we want to add this experimental behavior behind a preference so that webcompat team can use it, it can be done pretty easily. I will submit a basic patch doing that. If anyone wants to pick it up, polish it, add tests and try to review the behavior on more examples, I can't imagine this would take more than a few days of implementation + review.