Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
nextTick implementation breaks with core-js@3 Promise polyfill on Tizen 2016
See original GitHub issueVersion
2.6.11
Steps to reproduce
Just cross-linking the issues here, it was opened in core-js repo: https://github.com/zloirock/core-js/issues/814
The reproduction is not easily doable as it requires a Samsung Tizen 2016 device (which I have because I develop specifically for TVs).
What is expected?
UI updates correctly after events
What is actually happening?
UI will only update if another task is queue.
In the nextTick implementation there’s a check for isIOS to trigger an extra setTimeout which, while hacky, works also for Tizen 2016.
Perhaps a PR could be made adding an exception for Samsung Tizen as well?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
A boiled down repro is still required
@posva a simple fix would be to detect Tizen user agent and do the same trick as it’s done for iOS (using a setTimeout), but I noticed an impact in performance while doing user interaction e.g with longpress. I’m curious to know why it worked with core-js@2 with no special quirks.
One solution for me to move forward now is to use core-js v2 on this project, but it seems like going against the grain, as v2 is already deprecated in favor of v3. I don’t want to send a PR unless it’s absolutely necessary.