Meet the browser: Chrome Next


Recommended Posts

  • 2 weeks later...

Anyone know of a bug to track with Chrome's D2D support

where having D2D turned on makes certain fonts extremely bold (compared to D2D off)? (FF / IE not exhibiting this problem)

Link to comment
Share on other sites

Anyone know of a bug to track with Chrome's D2D support

where having D2D turned on makes certain fonts extremely bold (compared to D2D off)? (FF / IE not exhibiting this problem)

 

I had same issue in M37 where certain fonts got bold but eventually in M39 they fixed that, I would recommend you to try Chrome Canary to see whether that issue which I had got fixed for you or not.

Link to comment
Share on other sites

 

  • Canvas: Software only, hardware acceleration unavailable

     Accelerated 2d canvas is disabled on Windows systems with low perf stats

 

Canvas acceleration is disabled with last build on Windows 8.1 due to low perf stats, but I don't think my computer is low-end.

 

 

Which GPU Driver you have installed? Vendor + Model + Driver versions

Link to comment
Share on other sites

Intel HD 3000 + Nvidia GT 630M. Latest driver versions.

 

You are using Laptop (M on end of nvidia GPU indicated it), so it could be possible regression in Chrome side so they disabled it. I suggest you to install sideway Canary build to see whether they fixed it on that or not. Also confirm latest GPU version from both below. Lastly, I will suggest to file bug on: https://code.google.com/p/chromium/issues/list

 

Intel latest GPU:

32-bit - https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23763〈=eng&ProdId=3319

64-bit - https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23764〈=eng&ProdId=3319

 

Nvidia Latest WHQL driver from here: http://www.geforce.com/drivers

 

 

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

Chrome Team might backport Battery Friendly last piece patch to M38, so it can be assumed, Chrome 38 will be much more battery friendly then current one:

 

Link: https://code.google.com/p/chromium/issues/detail?id=153139#c93

Link to comment
Share on other sites

DirectWrite improvement:

 

 

[DirectWrite] Add support for font-stretch suffixes

Add support for font family names with a font-stretch suffix (such as
Condensed, UltaExpanded, Narrow etc). If the full name fails to match an
installed font check for a font-stretch suffix and if so strip it and
set the stretch value according to the suffix.

The current implementation matches IE when it comes to picking or
overriding the stretch value based on the suffix.

 

https://chromium.googlesource.com/chromium/blink/+/d44ec3a3942b030678b6f48df993ca7312a5e216

Link to comment
Share on other sites

So what interesting flags should we be looking out for?

 

I enabled (in Chrome Beta v38):

  • Show Autofill predictions
  • Built-in Asynchronous DNS (I read elsewhere that this is flagged for removal since May last year?)
  • Enable Download Resumption (have not tested this yet)

After resetting all to default, because I couldn't remember what I did before :p After checking Plugins I also saw that both Flash plugins were enabled, so I disabled the Adobe one, I get mixed results with Flash and have HTML5 enabled on YouTube anyway.

 

I like the new profile switcher thing.

Link to comment
Share on other sites

Did 38 Beta change the way it handles Plugins? I have a DVR system that uses a "WebKit" plugin. Every since 38 Beta, the Browser when you try to go to the DVR page, thinks the plugin is not installed. But it is. If I test it on 37 stable, it still works fine.

 

I'm guessing when 38 goes Stable, I'll lose the ability to access my DVR system 100% in Chrome at that time. Anyone have any ideas? It's a Q-See DVR.

 

DVR Client Version: 1,1,2,34
Web Camera
Name: DVR Client
Description: Web Camera
Version: 1,1,2,34
Location: C:\windows\system32\WebClient\npwebclient.dll
Type: NPAPI
  Disable
MIME types: MIME type Description File extensions application/x-dvrwebclient npwebclient  
Link to comment
Share on other sites

 

Did 38 Beta change the way it handles Plugins? I have a DVR system that uses a "WebKit" plugin. Every since 38 Beta, the Browser when you try to go to the DVR page, thinks the plugin is not installed. But it is. If I test it on 37 stable, it still works fine.

 

I'm guessing when 38 goes Stable, I'll lose the ability to access my DVR system 100% in Chrome at that time. Anyone have any ideas? It's a Q-See DVR.

 

DVR Client - Version: 1,1,2,34
Web Camera
Name: DVR Client
Description: Web Camera
Version: 1,1,2,34
Location: C:\windows\system32\WebClient\npwebclient.dll
Type: NPAPI
MIME types: MIME type Description File extensions application/x-dvrwebclient npwebclient

 

I read somewhere that NPAPI plugins aren't supported in the 64-bit version of Chrome, so if that's what you are using, that is likely the reason.

 

I only saw it because I searched for "issues with the 64-bit version of Chrome" (for another reason) anyway I have since gone back to the 32-bit beta channel (v38) from the 64-bit v37 stable version.

Link to comment
Share on other sites

I read somewhere that NPAPI plugins aren't supported in the 64-bit version of Chrome, so if that's what you are using, that is likely the reason.

 

I only saw it because I searched for "issues with the 64-bit version of Chrome" (for another reason) anyway I have since gone back to the 32-bit beta channel (v38) from the 64-bit v37 stable version.

 

Yeah I see that, just checked some searches, but I am using 32bit. What happen is, when the DVR web-page checks to see if the Plugin is installed, it apparently can't and says "install the plugin". Wonder if there is some way I can trick it.

Link to comment
Share on other sites

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