Skip to content
This repository was archived by the owner on May 25, 2021. It is now read-only.

FireFox compatibility using WebExtensions format. #1268

Merged
merged 10 commits into from
Mar 22, 2018

Conversation

santiago-elustondo
Copy link
Contributor

@santiago-elustondo santiago-elustondo commented Jan 24, 2018

issue: #1150

@santiago-elustondo
Copy link
Contributor Author

santiago-elustondo commented Jan 24, 2018

todo at this point:

We could either ignore certain parsing errors on mozilla's end, edit the manifest such that it does not use unsupported features, or create 2 separate manifest files.

@@ -0,0 +1,44 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of maintaing complete manifests for each browser, I’m wondering if having a base template and merging differences per browser might be more maintainable?

This could be done using object literals that get merged together and then saved as the final manifest.json file.

package.json Outdated
"build": "webpack --colors --display-error-details --display-cached",
"build-chrome": "cross-env BROWSER=chrome npm run build",
Copy link
Contributor

Choose a reason for hiding this comment

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

I personally like using the namespace:task convention for npm scripts. For instance:

build: '...',
build:prod: 'npm run build:prod:chrome && npm run build:firefox',
build:prod:firefox: '...',
build:prod:chrome: '...'

sumitarora
sumitarora previously approved these changes Feb 2, 2018
Copy link
Member

@sumitarora sumitarora left a comment

Choose a reason for hiding this comment

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

looks good awesome :D

Copy link
Contributor

@andrewthauer andrewthauer left a comment

Choose a reason for hiding this comment

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

@santiago-elustondo - Looks good! Did you still have outstanding manifest questions?

@santiago-elustondo
Copy link
Contributor Author

no outstanding manifest questions

andrewthauer
andrewthauer previously approved these changes Feb 9, 2018
@potch
Copy link

potch commented Feb 9, 2018

Hello! I'm Potch, from Mozilla dev advocacy.

I built this branch locally and loaded the extension into Firefox to test it out. It seems to be working, but do you have any specific test apps I can point it at to verify?

Thanks for putting in the leg-work to port!

@sumitarora
Copy link
Member

@potch You can test any of the Angular 2+ applications. We use this as the base application to check https://github.com/rangle/augury-examples/tree/master/kitchen-sink-demo If you want to check just run the application and test it in Firefox :D

@potch
Copy link

potch commented Feb 12, 2018

I wasn't able to get the kitchen-sink-demo to build, but tried it on https://angular-quickstart.glitch.me/ and got the expected panel and was able to browse the (admittedly tiny) component tree. Excited to see this working!

@santiago-elustondo santiago-elustondo changed the title (Work In Progress): FireFox compatibility using WebExtensions format. FireFox compatibility using WebExtensions format. Feb 15, 2018
sumitarora
sumitarora previously approved these changes Mar 10, 2018
@abdulkareemnalband
Copy link

What is the status of this PR?

@andrewthauer
Copy link
Contributor

We are currently working to get Augury approved in the Firefox add-on store. We hit a small issue with the add-on size which is being investigated. In the short-term you could pull the PR branch, build the add-on, then install the add-on from a file.

@santiago-elustondo santiago-elustondo changed the base branch from master to dev March 22, 2018 20:09
@santiago-elustondo santiago-elustondo merged commit 6224b0f into rangle:dev Mar 22, 2018
@digitarald
Copy link

@andrewthauer it looks like the referenced AMO issue will not be fixed soon (as not many extensions are known to be blocked by this, so it is hard to make weigh risks vs benefits; working on it). Are you waiting on this or are you still working on splitting/reducing JS bundle size?

@andrewthauer
Copy link
Contributor

@digitarald we are good now. We were able to get the bundle size down and I was able to successfully submit the add-on. Just a few final tweaks and it should be ready to go very soon.

Thanks for following up. Looks like the AMO issue can be closed. Anything else you can think of that we should look at or do before publishing?

@digitarald
Copy link

@andrewthauer looks like you submitted? Did it all work out?

@andrewthauer
Copy link
Contributor

andrewthauer commented Mar 29, 2018

@digitarald we did. It was initially approved, then disabled after another AMO review. There are a 4 issues that we will have to work though before re-submitting it looks like. I haven't had a chance to review them in detail so I'm not sure on the scope of change required yet.

@digitarald
Copy link

Our review process is a little more involved, hopefully it doesn’t cause too much extra work. If anything is unclear, you can ask the reviewers by replying to the review email. Feel free to loop me in as needed.

santiago-elustondo added a commit that referenced this pull request Apr 11, 2018
* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)
@andrewthauer
Copy link
Contributor

Thanks @digitarald! I've followed up with some additional questions for the reviewer. I'll reach out to you if we run into any problems.

@santiago-elustondo santiago-elustondo deleted the ff-compat branch April 23, 2018 16:11
santiago-elustondo added a commit that referenced this pull request Apr 30, 2018
* Release (1.16.0) (#1284)

* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)

* remove update_url from manifest.json for chrome

* Update CHANGELOG (1.16.0)

* Release (1.16.0) - Tag Version
santiago-elustondo pushed a commit that referenced this pull request Apr 30, 2018
* Release (1.16.0) (#1284)

* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)

* remove update_url from manifest.json for chrome

* Update CHANGELOG (1.16.0)

* tag version

* #1289: set script.textContent only if the document is HTML (Avoids breaking Firefox XML formatter)
santiago-elustondo added a commit that referenced this pull request May 7, 2018
* Release (1.16.0) (#1284)

* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)

* remove update_url from manifest.json for chrome

* Update CHANGELOG (1.16.0)

* Release (1.16.0) - Tag Version

* add build configs accessible from code

* explanatory note on types

* merge in all build configs

* correction

* clean up env config

* linter

* touchups

* linter

* csp update
santiago-elustondo added a commit that referenced this pull request May 16, 2018
* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)

* Update dev branch to match master. (#1292)

* Release (1.16.0) (#1284)

* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)

* remove update_url from manifest.json for chrome

* Update CHANGELOG (1.16.0)

* Release (1.16.0) - Tag Version

* Fix firefox xml viewer (#1290)

* Release (1.16.0) (#1284)

* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)

* remove update_url from manifest.json for chrome

* Update CHANGELOG (1.16.0)

* tag version

* #1289: set script.textContent only if the document is HTML (Avoids breaking Firefox XML formatter)

* Upgrading to webpack 4 (#1285)

* Angular AOT Build (#1295)

* Upgrading to webpack 4

* Adding aot compilation support

* Removing uncessary imports in aot build

* version up for merge-jsons plugin. prev versions crash with Webpack4

* Fixing test and build

* local fonts (#1297)

* Build conditionals (#1296)

* Release (1.16.0) (#1284)

* fix bug: frontend doesnt clear error screen when app detected (#1274)

* FireFox compatibility using WebExtensions format. (#1268)

* modify manifest for compatibility

* add web extensions packing

* remove augury.xpi

* fix popup size in firefox

* browser-specific builds

* browser-specific builds

* manifest.json merging & npm script naming scheme

* uncomment sentry_key check

* add uglify

* add canary to builds

* add canary to builds

* version up

* add yihua fix

* linter

* version up

* Updating docs and text to reflect Firefox support (#1278)

* small patch for PrimeNG

* linter

* version up

* fix dependencies thing yet again

* version up

* include canary build in ISSUE_TEMPLATE.md

* Update README.md with canary

* remove comma

* version up for release (manifest)

* version up for release (package)

* remove update_url from manifest.json for chrome

* Update CHANGELOG (1.16.0)

* Release (1.16.0) - Tag Version

* add build configs accessible from code

* explanatory note on types

* merge in all build configs

* correction

* clean up env config

* linter

* touchups

* linter

* csp update

* use destructuring import

* json5-parsing

* version up

* linter

* fix function-name.ts (state bug)

* ready for release

* update package-lock.json
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants