Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


UCyborg last won the day on January 22

UCyborg had the most liked content!

Community Reputation

174 Excellent


About UCyborg

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

2,771 profile views
  1. I see, that other problem is not related. Here's a working link to Raymond Chen's blog post about this: https://web.archive.org/web/20190218192651/https://blogs.msdn.microsoft.com/oldnewthing/20120726-00/?p=7043 Probably best to wait until some more updates have already been pushed.
  2. The old parameter still applies to Chrome 75, the new one applies to Chrome 76. I guess only time will tell about the future versions.
  3. Wow! Might not be related, but:
  4. I checked the code, they just changed the command line parameter for disabling custom title bar. The correct parameter in newer Chromium browsers is -disable-windows10-custom-titlebar The decision is made in chrome/browser/win/titlebar_config.cc.
  5. Does FullEventLogView show them the same way?
  6. If anyone's interested, Vivaldi is one of the more interesting Chromium based browsers and has the option to enable native title bar (Use Native Window under Appearance in Tools->Settings). It doesn't put tabs on it in that mode.
  7. I think what you're trying to accomplish relies on the shell's internal logic, the option along with all supporting code would probably have to be added to the dialog that opens when you click Change desktop icons from Personalization control panel. So, since MS won't do it, the only option would be analyzing system DLLs and injecting new code into them, a non-trivial task I imagine.
  8. Thanks, this one works. Still find it odd; GreaseMonkey 3.11 doesn't have compatibility issues with Firefox 51. Waterfox on the other hand runs them all.
  9. There are already bugs with existing addons (at least with Basilisk). Options dialog in GreaseMonkey doesn't work. Also this particular fork's default configuration breaks ColorfulTabs (it expects Firefox version number in the user agent string).
  10. The option is really gone in Chromium 76. They removed conditional check (feature toggle via command line parameter) that used to enable native caption bar. There's no hidden registry setting for it or anything like that.
  11. Moonchild Productions ported the custom caption bar drawing code to their Pale Moon fork as well, see this thread. You'll find my comparison screenshots if you scroll down a bit. They say there would be visual glitches on Windows 10 without custom caption bar drawing, but I don't see anything off with the native caption bar. The caption text is always enforced by Pale Moon, the only other difference I can see is spacing between min/max/close buttons and the caption bar height (I might have reduced default caption height setting in Windows, but I'm not 100% certain). So honestly, I've no idea what they're talking about. Looks like the only option that still exists in the current nightly is setting browser.tabs.drawInTitlebar in about:config to false to enable the native caption bar (and put tabs separately). CSS moz-win-glass property is indeed gone.
  12. Back when I wrote my last post here, policy setting for InPrivate mode was still called IncognitoModeAvailability. Now it's called InPrivateModeAvailability. There's also -inprivate command line parameter that is accepted by msedge.exe, equivalent to Chromium's -incognito.
  13. Recently experienced the same issue. I was trying to boot one of OSes I have on the USB flash drive and it failed. Plugging the drive in a running Windows machine showed it as unformatted. Could access the data from Linux, TestDisk showed invalid boot sector and some unimportant files were corrupted. I could probably avoid reformatting if I knew the correct numbers for drive geometry (they were different than after format). At the end, I also had to change drive's unique ID with diskpart because it apparently changed to the exact same one my laptop's disk has, so Windows refused to mount it. I'm certain the actual cause was loose connection. If you even slightly touch the drive so it moves just a little to the left or right when plugged in, it can lose power. That's how my laptop's ports are and the fronts ones on my desktop aren't much better.
  14. Yes, it seems they have to be made specifically for non-default taskbar configurations. When I have more time and if I figure out how to do file selection and such.
  15. I wonder how much effort it actually takes to provide 32-bit builds. Is it just the compilation part or are there also significant chunks of processor specific code? Graphics cards with 2 GB of video RAM were already common in low-mid price range 5 years ago. So that takes the half of the 32-bit addressable space, so one can use 2 GB RAM max. 4 GB card would take that number down to zero. Then there's PAE, which, AFAIK, on today's Windows can only be utilized by unofficial patches to the kernel (assuming drivers in use on the particular system aren't buggy).
  • Create New...