Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Add HTTP Nowhere mode to Chromium - #603

Closed
diracdeltas wants to merge 3 commits into
4.0from
feature/http-nowhere-chrome
Closed

Add HTTP Nowhere mode to Chromium#603
diracdeltas wants to merge 3 commits into
4.0from
feature/http-nowhere-chrome

Conversation

@diracdeltas

Copy link
Copy Markdown
Contributor

Adds mode for blocking HTTP requests entirely after HTTPS Everywhere
rewrites. Switches UI button from PageAction to BrowserAction.

Adds mode for blocking HTTP requests entirely after HTTPS Everywhere
rewrites. Switches UI button from PageAction to BrowserAction, because
why was it a PageAction in the first place?
@semenko

semenko commented Sep 27, 2014

Copy link
Copy Markdown
Contributor

Nice work! I'll review this in a bit.

What are your thoughts on the pageAction -> browserAction switch and the UX change? (I think I'd added that comment originally)

@semenko

semenko commented Oct 16, 2014

Copy link
Copy Markdown
Contributor

Friendly ping @diracdeltas -- thoughts on pageaction vs browseraction switching? I'd added that comment originally, though now I have mixed thoughts. My chrome extension space is super busy ... and I kinda like that HTTPSe is hanging out with the URL address bar.

@jsha

jsha commented Nov 25, 2014

Copy link
Copy Markdown
Member

@semenko, @diracdeltas, what's the status of this? Still needs review?

@semenko

semenko commented Nov 25, 2014

Copy link
Copy Markdown
Contributor

Will take a look again, biggest point is this is really two changes.

One is a Chrome UX change that switches the HTTPSe icon from URL bar (pageaction) to on every page as a button (browseraction).

@jsha

jsha commented Dec 17, 2014

Copy link
Copy Markdown
Member

I think switching the icon to be a BrowserAction is fine. It's not consistent with browser guidelines, but it's consistent with our other plugin, Privacy Badger.

@semenko

semenko commented Jan 9, 2015

Copy link
Copy Markdown
Contributor

Ok -- taking a look at this now. @jsha should we be merging this into 4.0 vs master?

First notes: HTTP Nowhere mode doesn't seem to be working 100% for me. Some pages (Chrome prerender replaced?) seem to bypass this mode. Will update / patch.

@jsha

jsha commented Jan 9, 2015

Copy link
Copy Markdown
Member

Let's merge to master, since I'll be promoting master to stable sometime this month.

@semenko semenko self-assigned this Jan 9, 2015
Comment thread chromium/manifest.json

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just being explicit, since this is a dangerous file to change: 'storage' does not cause additional permissions warnings, per:
https://developer.chrome.com/extensions/permission_warnings

@jsha

jsha commented Feb 15, 2015

Copy link
Copy Markdown
Member

How's this going?

@semenko

semenko commented Feb 15, 2015

Copy link
Copy Markdown
Contributor

Fell to the back burner for a while -- will take a look soon

@diracdeltas

Copy link
Copy Markdown
Contributor Author

Let me know if you need help on getting this merged!

Also, note that this introduces use of chrome.storage.sync for extension prefs. I think that's a good move, since it can be used for #1022.

@semenko

semenko commented Mar 9, 2015

Copy link
Copy Markdown
Contributor

Sorry, still on the back burner until a few more things are hammered out for a manuscript.

Last I checked, this wasn't working as expected -- I think prerendered tabs were ignored, or something similar.

(At the least, I'll break out the UX change into a separate PR)

@semenko

semenko commented Mar 26, 2015

Copy link
Copy Markdown
Contributor

Ok -- tracked down the bug in this. Will rebase and probably open a new PR (since i'm hesitant to ever use git --force ...)

@semenko

semenko commented Mar 26, 2015

Copy link
Copy Markdown
Contributor

rebased & opened #1295

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants