New Flash Player 11.3.300.270


Recommended Posts

Has anyone else noticed how the youtube player UI messes up when the page is scrolled? I noticed it happening a few weeks back. Is this a Flash issue or a youtube issue?

it's a firefox issue as far as i'm aware, it doesn't happen in chrome for me just firefox

i think it has to do with how firefox has its smooth scrolling set up

it's a firefox issue as far as i'm aware, it doesn't happen in chrome for me just firefox

i think it has to do with how firefox has its smooth scrolling set up

I'm not too sure about that as I have the same issue with computers running IE9 and IE10 at the moment.

I'm not too sure about that as I have the same issue with computers running IE9 and IE10 at the moment.

hmm, I wonder what chome's doing differently then that it doesn't happen with the same version of flash

It does sound very strange, am I correct in believing that Chrome has a special version of flash baked in though which may be slightly modified from the core versions?

AFAIK it's not modified at all, just baked in (which you can still disable and use the version on your computer, which still the issue doesn't appear[at least it didn't for me])

I am stumped then, I just tested it on a couple of other websites with flash banners at the top of the page and the problem occurs there as well, if flash is enabled the page blurs when scrolling until you scroll up and down slightly, with flash disabled no such issue. Are you testing it on Windows or OSX though?

I am stumped then, I just tested it on a couple of other websites with flash banners at the top of the page and the problem occurs there as well, if flash is enabled the page blurs when scrolling until you scroll up and down slightly, with flash disabled no such issue.

what browser?

AFAIK it's not modified at all, just baked in (which you can still disable and use the version on your computer, which still the issue doesn't appear[at least it didn't for me])

Its uses PPAPI rather NPAPI... plugin interface.. PPAPI which is standardized by Google (if wrong correct me).. As far as Mozilla does not have plan to implement it soon so PPAPI gives edge of Chrome Metro on Win8 having Plugin support etc.. So overall Flash in Chrome is quite different than others.

But as far as I know the PPAPI version of Flash in Chrome is older than the currently released version. The draw issues when scrolling are very common on Firefox, Internet Explorer and Opera. Very annoying too.

i'll agree with you there, it's a very annoying bug :/

AFAIK it's not modified at all, just baked in (which you can still disable and use the version on your computer, which still the issue doesn't appear[at least it didn't for me])

How do you disable the internal Chrome Flash plugin? I'm still searching for a way to set the browser completely back to defaults. I've probably messed it up so much trying to fix these Flash issues.

How do you disable the internal Chrome Flash plugin? I'm still searching for a way to set the browser completely back to defaults. I've probably messed it up so much trying to fix these Flash issues.

chrome://plugins
Today, Flash Player 11.3.300.270 for Windows was released to address a crash that was occurring in the Adobe Flash Player Update Service (FlashPlayerUpdateService.exe). There are no other fixes or changes provided with this build.

http://forums.adobe.com/thread/1043626?tstart=0

so is this a windows only update? ive been scouring lookin for the mac version of this but to no avail .. on my 2 windows machines even though the download page listed .268 it still delivered .270 , but on my MBP i still continue to only get .268 .. hmm?

so is this a windows only update? ive been scouring lookin for the mac version of this but to no avail .. on my 2 windows machines even though the download page listed .268 it still delivered .270 , but on my MBP i still continue to only get .268 .. hmm?

Read what the link says - it clearly states that 11.3.300.268 is the latest version.

This topic is now closed to further replies.
  • 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!