We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I want to show the browser-action-list inside the browserView which could be located anywhere on the screen. ( Lets call it containerView )
browser-action-list
browserView
containerView
When user clicks on the browser-action it calculates the position of the popup window by getting the boundingRectangle of the html element.
browser-action
As a result popup is opened in a wrong position on the screen because it doesn't consider bounds of the containerView
Add offset properties to the browser-action-list component that will be added to the boundingRectangle coordinates.
offset
<browser-action-list offset-x="100" offset-y="150"></browser-action-list>
The text was updated successfully, but these errors were encountered:
The 'browser-action-popup-created' event is emitted once one is created. Would it be possible for you to adjust the position within an event listener?
Alternatively, logic to check the container bounds could be added to the code which positions the popup.
Sorry, something went wrong.
No branches or pull requests
Problem
I want to show the
browser-action-list
inside thebrowserView
which could be located anywhere on the screen. ( Lets call itcontainerView
)When user clicks on the
browser-action
it calculates the position of the popup window by getting the boundingRectangle of the html element.As a result popup is opened in a wrong position on the screen because it doesn't consider bounds of the
containerView
Possible solution
Add
offset
properties to thebrowser-action-list
component that will be added to the boundingRectangle coordinates.The text was updated successfully, but these errors were encountered: