Closed
Bug 1582080
Opened 5 years ago
Closed 2 years ago
Expanding event object causes warning message: "MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead."
Categories
(DevTools :: Debugger, defect, P3)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 860312
People
(Reporter: Honza, Unassigned)
References
(Blocks 1 open bug)
Details
STR:
- Load http://janodvarko.cz/xhr-spy/
- Create
Mouse -> click
DOM BP - Check the
Log
checkbox - Click on the page
- Check out the Console panel, there should be three
click
logs - Expand and collapse the first log
- You should see
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead.
warning -> BUG
ER: the warning shouldn't be there
Honza
Reporter | ||
Updated•5 years ago
|
Blocks: dbg-event-bps
Reporter | ||
Comment 1•5 years ago
|
||
Note that logging on events was introduced in bug 1110276
Honza
Comment 2•5 years ago
|
||
This isn't related to logpoints, as the following STR would produce the same effect:
- Navigate to
data:text/html,<meta charset=utf8><script>document.addEventListener("click", console.log)</script>
- Click on the page
- Open the console
- Expand the logged object in the console
I know for sure that we already have a bug for that, but I can't find it anymore. Basically it's because we iterate over the object when retrieving the properties, which makes the engine emit those warnings. We discussed in the other bug trying to filter out these messages from the console by looking at their stack.
Updated•5 years ago
|
Summary: DOM Mutation Logs should not log "MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead." → Expanding event object causes warning message: "MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead."
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
Comment 4•2 years ago
|
||
Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 860312
Flags: needinfo?(nchevobbe)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•