9.11.0 offsetX work arounds
See original GitHub issueHey guys, 9.11.0 created a problem with some of my tests. My code does math based on sizes of dom nodes. I was previously able to do something like
node.offsetTop = 100;
Now, I’m just getting errors about not having setters. Is there way you are aware of me being able to work around this? For now I’m hard fixing to 9.10.0.
Thanks so much for this library. It is truly great!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
TS 136 104 - V9.11.0 - LTE - ETSI
3GPP TS 36.104 version 9.11.0 Release 9. Reference. RTS/TSGR-0436104v9b0. Keywords. LTE. ETSI. 650 Route des Lucioles. F-06921 Sophia Antipolis Cedex - ...
Read more >MouseEvent.offsetX - Web APIs - MDN Web Docs
The offsetX read-only property of the MouseEvent interface provides the offset in the X coordinate of the mouse pointer between that event ...
Read more >Release Notes — GraphDB SE 9.11.0 documentation
GDB-6324 Authentication to FedX generic SPARQL endpoint does not work ... GDB-6431 CONSTRUCT query with both LIMIT/OFFSET and ORDER BY fails with an...
Read more >Changelog for BIND 9.11.0 - ABI laboratory
[port] Changed the bin/python Makefile to work around a bmake bug in FreeBSD 10 and NetBSD 6. [RT #36993] 3949. [experimental] Experimental support...
Read more >8. Configuration Reference — BIND 9 9.18.8 documentation
Dual-stack servers are used as servers of last resort, to work around problems in reachability due to the lack of support for either...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
should work.
What’s the correct way to achieve this with
Object.defineProperty
?I’ve tried the following, but it creates an infinite loop (which makes sense):
Hardcoding the property on the global
HTMLElement
is also not quite what I want.