Skip to content
New issue

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

firefox compatibility adjustments #77

Open
wants to merge 5 commits into
base: next
Choose a base branch
from

Conversation

RobertFridolin
Copy link
Contributor

@RobertFridolin RobertFridolin commented Jun 14, 2024

fix: small adjustments for firefox compatibility

#5

small adjustments for firefox compatibility
@RobertFridolin
Copy link
Contributor Author

RobertFridolin commented Jun 14, 2024

these are only preparations to hande different browsers that should otherwise have no consequences
no problem-free Firefox compatibility yet

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you explain what this does?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maps firefox specific API to chrome api naming for example browser.storage.local.get to chrome.storage.local.get

@@ -76,6 +76,7 @@ class AboutDialog {
<img src="${chrome.runtime.getURL('images/AES-logo-128.png')}">
<h2>AirlineSim Enhancement Suite</h2>
<p>Version ${version}</p>
<p>Browser ${window.navigator.userAgent}<p>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What’s your motivation for putting the userAgent string in the AES about screen?

Copy link
Contributor Author

@RobertFridolin RobertFridolin Jun 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was for debug purposes if someone sends you a bug report on discord you have the AES version and exact browser version right there, in case there are browser-specific problems
if it bothers you, it can also be removed/shortened or moved elsewhere or hidden behind a "debug information" button or something

make site load detection more robust by checking
for readystate=complete because the load event might get missed

fix data saving by not saving methods in database, makes no sense doing so?

ZoeBijl#5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants