Recommended Posts

  • 2 weeks later...

Google PDF Renderer Open Sourced now: https://code.google.com/p/pdfium/

 

Rather than from Adobe it was actually from Foxit.

 

http://www.i-programmer.info/news/136-open-source/7433-google-open-sources-pdf-software-library.html

 

 

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

New Collect Errors Option for extension under Developer Mode:

v3RyF0S.png

 

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

Also Chrome is removing GTK theme code in favour of Aura on Linux. If you face it broken, you can guess it is gone now.

M38 development started.

Chromium 32-bit development shifted to now Git, now unlike previously there is no proper changelog in text format in snapshot folders and snapshots also appear randomly. I shifted my default Chromium 64-bit which does not yet suffered similar fate.

Maybe I just missed it but why did they disable smooth scrolling?

Are you talking about the smooth scrolling flag in about:flags? If so, that's been disabled for a while now, and they disabled it because it doesn't work with threaded compositing.

Are you talking about the smooth scrolling flag in about:flags? If so, that's been disabled for a while now, and they disabled it because it doesn't work with threaded compositing.

 

That's what I was referring to yes. So I guess I did miss something.

I'm wondering if Google gave the devs a vacation, hence the lack of new Chromium builds for the last week.

 

Yeah, 64-bit builds are no longer happening, I asked them on chromium-discuss google group but no response so far.

For 32-bit builds, they shifted to Git which does not provide simple xml format changelogs.

 

To get latest 32-bit build:

- Move to end (use END button from Keyboard)

- Read LAST_CHANGE file in new tab and copy paste string

- Go back to 32-bit snapshots tab and press F3 or Ctrl+F and find string matching folder

 

It will be latest... I found latest through this... I uninstalled 64-bit (I went to them after they switched to Git but they are no longer maintaining them on that branch IMO).

Can anyone get Chrome x64 to work with Hyper-V enabled?  I haven't tested without Hyper-V yet but everytime I start Chrome x64 it crashes straight away and I suspect Hyper-V is the reason.

Does this reveal any hyper-v relevant .dll? or any crash id?

 

chrome://crashes/

 

chrome://conflicts/  

Looks like smooth scrolling is finally coming back, they've got a new impl-side implementation:

 

The following revision refers to this bug:

https://chromium.googlesource.com/chromium/src.git/+/749cbc62498edd705dba6138f924a82c75274c88

commit 749cbc62498edd705dba6138f924a82c75274c88
Author: [email protected] <[email protected]@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Thu Jul 10 01:06:35 2014

Impl thread smooth scrolling.

This is a first pass at smooth scrolling on the compositor thread. It adds LayerTreeHostImpl::ScrollAnimated, which kicks off a scroll offset animation through the layer animation controller.

When the --enable-smooth-scrolling flag is present, InputHandlerProxy will call ScrollAnimated for composited wheel scrolls.

Once this is in the next steps are:

(1) Update the animation curve to aim at a new target when a wheel event comes in while a scroll animation is in progress. (For now we just drop the event.)

(2) Unify the behavior with WebCore::ScrollAnimatorNone. We should be able to share a lot of logic since cc::ScrollOffsetAnimationCurve is already exposed to Blink through compositor bindings (for http://crbug.com/243871).

BUG=575

Review URL: https://codereview.chromium.org/361143002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282205 0039d316-1c4b-4281-b951-d872f2087c98

Looks like smooth scrolling is finally coming back, they've got a new impl-side implementation:

 

I really hate new Chromium Git shift and no update to 64-bit continuous builds... Since I can't read changelogs now...

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
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!