Https-everywhere: Release 2018.6.12 forthcoming

Created on 9 Jun 2018  路  15Comments  路  Source: EFForg/https-everywhere

Type: other

cc @jsha @pde @J0WI @diracdeltas @jeremyn @gloomy-ghost @Bisaloo

Let's come up with some release notes in the comments, as well.

Release notes:

2018.6.12 
  * Improve popup page performance and slightly reduce memory usage
  * Measure and slightly improve memory usage for rulesets
  * Fix CORS issues in Firefox. This bug was previously breaking embedded videos or css on many websites. Chrome browser was not affected by this bug
  * Add "Reset to Defaults" option to reset the default ruleset states
  * Add "Show Devtools tab" option to hide CDT tab
release-forthcoming

Most helpful comment

4510 actually reports multiple multiple issues. One of them was CORS related and fixed in https://github.com/EFForg/https-everywhere/pull/14656. The other is caused by MCB and a fix is pending in https://github.com/EFForg/https-everywhere/pull/14913.

All 15 comments

Good start with the commit titles from the great work of @cschanaj

2018.6.12 
  * Improve popup page performance and slightly reduce memory usage
  * Fix some CORS issues in HTTP Nowhere mode
  • Fix CORS issues in Firefox. This bug was previously breaking embedded videos or css on many websites. Chrome browser was not affected by this bug.
  • Add "Reset to Defaults" option to reset the default ruleset states (#15411)
  • Add "Show Devtools tab" option to hide CDT tab (#15192 by @gavinhungry)

By the way, it would be nice to get #15387 merged for this release.

Maybe also this fix/cleanup of Danish translations.

https://github.com/EFForg/https-everywhere/issues/15482 was fixed so it should be mentioned as well

I don't have much time free tomorrow so I'm pushing this release to Wednesday

@Giltyhub that fixed a regression which was made after the last release, so this wouldn't really be delivering a fix. That's my main reservation for including #15482

I've added the release notes to the issue description. Let me know if I've missed anything.

For consistence and simplicity, maybe we don't need a reference to the PR in the release note?

also no need for the point at the end line of the third line (sorry by the way Github flagged my account for no reason and this message may not appear to you before a while...)

Thanks, I've removed the PR #'s

By the way, is it possible to close #8592 and close #4510 given #15157 is merged? They have been marked as CORS-bugs and been opened for some time.

4510 actually reports multiple multiple issues. One of them was CORS related and fixed in https://github.com/EFForg/https-everywhere/pull/14656. The other is caused by MCB and a fix is pending in https://github.com/EFForg/https-everywhere/pull/14913.

Release made!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

a0193143 picture a0193143  路  4Comments

00h-i-r-a00 picture 00h-i-r-a00  路  4Comments

cschanaj picture cschanaj  路  3Comments

J0WI picture J0WI  路  4Comments

jsha picture jsha  路  3Comments