Recommended Posts

  • 2 weeks later...

It seems that NPAPI has been phased out from M42, my NPAPI flash plugin is not working with Chromium.  :/

 

NPAPI Flash is not even showing in chrome:\\plugins as well.  :shifty:

Not sure about this, but I think in v41 Chrome now uses DirectWrite for rendering UI text as opposed to GDI in the previous versions.

 

Yeah, I posted about Chrome switching to DW for GUI as well on few pages back.

Block NPAPI plugins by default

Add --enable-npapi flag in chrome://flags to support re-enable.

Source: https://chromium.googlesource.com/chromium/src/+/0539f2f5214fc17fdd5d1964be0ceedf98fdb9ce

 

 

To enable NPAPI, while we can:

 

chrome://flags/#enable-npapi

  • 2 weeks later...

I think Chrome beta to canary build has a bug on "Go Back" when starting from the Google Search page.

 

example:

New Tab > Search "pfsense" > Click on the "Download" link search result > Click on any link on the page (I clicked on the "here on the mirrors" link) > Click the Back button

Out of Process Iframes under this flag:

 

 

 

Expose --site-per-process in chrome://flags

 

Bug URL - https://code.google.com/p/chromium/issues/detail?id=99379

Commit URL - https://chromium.googlesource.com/chromium/src/+/e52b234b38b4757408fa13364c283002bedfbcd6

 

-------------------------------------------------------------------------------------------------

Enable Roboto font in URL for testing purpose (Don't know on which devices and OSes)

 

 

 

Enable Roboto by default for testing purpose.

The testing team wants to enable 'Roboto' by default and have real users to help report bugs too.

In this CL 'Roboto' is enabled by default and can be disabled by going to chrome://flags and turn 'disable-roboto-font-ui' to on.

Also modify the OobeWebUITest to make the tests run in full screen, otherwise the tests will fail due to the incorrect layout of supervised user creation UI (based on xiyuan@'s advice).

BUG=448948 (Private - not opening)
TEST=tested on device (Pixel)

 

Commit URL - https://chromium.googlesource.com/chromium/src/+/b138032ecd37b1225ac200f561d6232d423dd89a

 

--------------------------------------------------------------------------------------

 

New flag for Privacy Improvement - "chrome://flags/#reduced-referrer-granularity"

 

Blog post on it - http://www.androidpolice.com/2015/02/05/chrome-v41-includes-privacy-friendly-flag-reduce-referrer-information-http-headers/

Support for HTTP/2 will be rolled into Chrome 40 over the next few weeks, but SPDY will remain operational at least until early 2016. This should give developers about a year to migrate to the new protocol, or simply allow their servers to fall back to HTTP/1.1, like they currently do for many other browsers. Alongside the removal of SPDY, Google also plans to remove support for the Transport Layer Security (TLS) extension NPN, and replace it with ALPN. A number of implementations have been recommended to help developers adopt HTTP/2 and ALPN on their servers.


Been a while since HTTP saw an update. I remember back when 1.1 came out the big change (among many) was compression, connection keepalive, and support for resuming downloads.

1991 - HTTP/0.9
1996 - HTTP/1.0
1999 - HTTP/1.1
2015 - HTTP/2.0


You can enable HTTP/2 right now if you want to. Go to chrome://flags and 'Enable' the setting below. Restart Chrome.

Enable SPDY/4 Mac, Windows, Linux, Chrome OS, Android
Enable SPDY/4, which is the HTTP/2 standard. Currently experimental. #enable-spdy4

I think Chrome beta to canary build has a bug on "Go Back" when starting from the Google Search page.

 

example:

New Tab > Search "pfsense" > Click on the "Download" link search result > Click on any link on the page (I clicked on the "here on the mirrors" link) > Click the Back button

 

I confirm buggy Back button behavior, reliably reproducible when I visit some GitHub Repos.

Would it be worth it to start a thread about decent flags that can be set/used that aren't on by default? It could just be for Chrome, or for Chrome & Firefox?

 

I would be interested in such a thread after having to reset flags to get auto spell check in multiple languages working again!

Would it be worth it to start a thread about decent flags that can be set/used that aren't on by default? It could just be for Chrome, or for Chrome & Firefox?

 

I would be interested in such a thread after having to reset flags to get auto spell check in multiple languages working again!

 

or you can always ask here.

it's easier to have things in one place to easily find them or ask for help IMO.

  • Like 6

Would it be worth it to start a thread about decent flags that can be set/used that aren't on by default? It could just be for Chrome, or for Chrome & Firefox?

 

I would be interested in such a thread after having to reset flags to get auto spell check in multiple languages working again!

 

Yeah, it could be possible. What do you suggest?

 

From here you can find all command-line switches (from Google Developer, who updates it frequently) - http://peter.sh/experiments/chromium-command-line-switches/

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now