Window resolution abnormal

[syslot]

When I update the new version 1.0.13, the extension's window resuolution is abnormal.

[andrewnguonly]

@syslot, thanks for reporting the issue! What browser and browser version are you using?

[syslot]

I tested this with two browser:

1. Chrome with Version 122.0.6261.129 (Official Build) (x86_64)
2. Arc Version 1.37.0 (48361) Chromium Engine Version 123.0.6312.106

[andrewnguonly]

I'm testing with Chrome version 123.0.6312.107 and I can't reproduce the issue. I'll test with Arc next. The screenshot looks like it's from Arc.

[syslot]

this pic is captured in chrome

[andrewnguonly]

Can you inspect popup window and check the width of the popup class? What does it show?

I can reproduce the issue if I remove the width attribute of the popup class.

.popup {
  /* width: 550px; */
  padding: 10px;
}

[syslot]

It doesn't match the situation you described. For the reason that I can't find the popup segment in style. Is it unexpected width of the container?

[andrewnguonly]

The expected width of the popup is 550px, as specified in Popup.css. If you don't see the popup class, then something is very wrong 😅

Can you try deleting the dist folder/files and rebuilding the entire app (i.e. npm run build)?

[syslot]

The expected width of the popup is 550px, as specified in Popup.css. If you don't see the popup class, then something is very wrong 😅

Can you try deleting the dist folder/files and rebuilding the entire app (i.e. npm run build)?

Thanks for your reply.
I've fellowed your advice , remove all project source code and re-clone it. After execute cmd : npm run build and load the dist fold, I found two errors in my extension page; here are :

Is this the problem?

[andrewnguonly]

It's possible that there's a CSS class name collision with another extension. I'm going to update the class names to see if that helps.

[andrewnguonly]

@syslot, can you try version 1.0.14?

[andrewnguonly]

Hey @syslot, just checking in. Does version 1.0.14 resolve your issue?

[andrewnguonly]

Closing this issue for now. @syslot, if the issue is still present in the latest release, please re-open this issue. Thanks!