Issue metadata
Sign in to add a comment
|
Hover area is clipped when extension size changes (mainly height)
Reported by
taesu...@gmail.com,
Oct 31
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Open an extension that has a hover effect and changes its height 2. Allow the extension to change its height 3. Try to hover over an element with an :hover effect on the lower portion of the extension (any part of the extension that is longer (taller) than the original height of the extension 4. Hover effect should work on any portion within the original height of the extension but any area taller than the original height will not fire any hover effects in css What is the expected behavior? The CSS hover effect should render within areas larger than the original height of the extension. What went wrong? Hover effects still work within the original height of the extension but no longer work in any area outside the original height of the extension. Did this work before? Yes v69 Does this work in other browsers? Yes Chrome version: 70.0.3538.77 Channel: stable OS Version: OS X 10.13.6 Flash Version: I was able to replicate this with our extension's settings page. I can provide a test login if needed. But it seems like any extension that changes its height will no longer register a hover state if the height of the extension is larger than it's initial state. The hover state will work within the original height and width of the extension but any additional height will no longer force the hover state on those element. Scrolling the elements back into the original height and width of the extension allows the hover state to be activated again but scrolling them into the new area of the extension will again disable the ability to activate the hover state of those elements. https://chrome.google.com/webstore/detail/private-internet-access/jplnlifepflhkbkgonidnobkakhmpnmh?hl=en
,
Nov 1
As per comment #1, closing the issue as wontFix. Please feel free to raise a new issue if able to reproduce the issue again using latest chrome builds. Thanks...!! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by taesu...@gmail.com
, Oct 31