🐛 Bug - InViewport misbehaving
See original GitHub issueForma 36 bug report
Summary
This bug occurs within the rich-text
field editor from field-editors
.
If you type a forward slash (/
) within the rich text field editor a context pop-up menu comes up that allows for a certain set of actions.
If you’re on a small resolution or you have resized your browser window to be small and this context menu overflows, there’s constant flickering and jumping back and forth of this menu which makes it unusable.
Environment
Latest Chrome, latest OSx
Steps to reproduce
To reproduce this bug:
- Visit this link: https://github.com/contentful/field-editors/tree/master/packages/rich-text
- Resize your browser window to be very small
- Scroll down to the rich field text editor
- Type a
/
- Observe the context menu that pops up
Expected results
I expected the pop-up context menu to stay stable so that I can use it.
Actual results
The pop-up context menu constantly jumps around.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Error with instantiating a store explicitly in view - Stack Overflow
I instantiate a store explicitly, but when I load this view in Viewport, I find an error like this: Uncaught TypeError: Expecting a...
Read more >InView React Component - CodeSandbox
InView.js. InViewDemoBody.js. extendChildrenProps.js ... VS Code's tsserver was deleted by another application such as a misbehaving virus detection tool.
Read more >Bifrost 2.3.0.0 Release Notes | Autodesk
Bifrost 2.3.0.0 is a feature release with new features, performance improvements, and bug fixes. It is available for Maya 2019, 2020, and 2022...
Read more >DAZ just updated, now odd visual error when moving mouse - Daz ...
If I am viewing through that camera (called "Inside CAM") the problem is the persistent flashing. If using any other camera the problem...
Read more >Dragging Material from Asset Browser (Link mode) to Viewport ...
Short description of error. Dragging a Material from the Asset browser to empty Space in Viewport removes the Material from all objects in...
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 Free
Top 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
The RichText editor is still using our undocumented InViewport F36 component. In F36 we no longer use this component and instead use popper.js.
So there are two things needed - update the RichText editor to use popper.js (so not for this repo), and, then finally remove InViewport.
I’ll work on updating the RichText editor and once a PR is open I’ll link this issue.
Hi,
InViewport component got removed in version 4.
If you need to use InViewport for any situation, we recommend checking out a react hook that allows using the IntersectionObserver declaratively in your React app to find out if an element is in a given viewport.