NotHereToPlayGames

It could be that all of the descriptions, product names, and product short names need to MATCH for Vista but XP and 10 just don't care about them not matching.

<sarcasm> Didn't you read? </sarcasm> It's all right there in the third post of this thread -- https://msfn.org/board/topic/185049-arcticfoxienotheretoplaygames-360chrome-v1352044-rebuild-1/?do=findComment&comment=1252587 It is the "crash reporting" that is edited out of the .exe and also the Chinese text. I wonder if it is the removal of the "crash reporting" or the removal of the Chinese file description, product name, or product short name? -- I could provide different versions of the .exe if you are truly interested in testing. I do not get the errors and you are the only one that does - doesn't make it invalid, of course, and we can fix it.

Of course I read it. Comments like "didn't you read" are condescending. Moving on... I kind of have to leave it at this. If the aswer to the above is "no", then we're kind of done here, don't you think? If the answer is "yes", then thanks in advance.

ps - by "I can run the original 2044 perfectly fine", are you also running 2044 with all of its "extra" .dll's and .dat's? Because I can "trace" with any disassembler and see the "errors" when exts.dat or sesafe.dll or seapp.dll or 360bdoctor.exe are being "hunted for" during launch. But same goes for all previous builds, all Humming Owl builds, and all Russian Repack builds. Aside from cloudurls.dat, only the files have been removed in all previous builds and that was always sufficient in the past.

Would you be willing to run different phases of the build instead of what was uploaded? ie, run "original" 2044's 360chrome.exe and chrome.dll then see what they do as I perform 10% of their updates, 20% of their updates, et cetera?

Unless I'm mistaken, you've had something similar in every version excluding your own 1030 (if I have you mistaken for another user, then apologies of course). Are you running your own "loader" instead of the one bundled "as-is"? Are you running any "real-time" virus program creating false positive with exception rules for your other browsers? FYI - the upside-down exclamation marks are removed from my skin, as is any "dark mode". So I would need you to PM me whatever skin/theme you are using to attempt any degree of a solution.

@rereser - I assume that when you are trying to get a bold font that you are using the Use system font size setting n conjunction with the XP theme settings?

Back burner low priority for me. I do intentionally hide the skin/theme button on my GUI. What's the point in removing Chinese telemetry if the GUI has a button taking you to a Chinese theme page? I've been meaning to do a Win10 theme one of these days. I still use the XP skin even when I'm on Win10.

I'll see if I can track it down. 2044 is technically the only version that didn't have a "Russian Repack" base. 2044 went straight from Chinese to English whereas other versions technically went from Chinese to Russian and then to English.

Let's not give up too soon. Perhaps you have to "apply" the theme, launch then exit 360Chrome, then revert and apply again. Have to make the theme changes and apply them when 360Chrome is not running. My default is Tahoma 8 regular - It's definitely changing to Arial Black 12 bold for me, then changing back to Tahoma 8 regular -

Cool. And correction - it appears 360Chrome only uses XP's Message Box theme settings (for font, bold/italic, and size but not for color).

I'm not quite sure I follow. Can you provide a screencap to illustrate?

I have that extension display:none hardcoded and it will always revert. I've technically always done it that way but I used to set the hardcode after uploading the "public version" without the display:none. @verta / @rereser -- The best I can determine is that build 1030, build 2022, build 2036, and build 2044 all are correct as far as the font setting BUT it SOMETIMES requires a "reset" when migrating between computers. To "reset" your theme's preferred font settings such as bold arial black, change a setting in your theme, revert it back, then APPLY all while 360Chrome is closed. Now open 360Chrome and you should see your bold arial black. Unsure what verta is using but the same applies, change a setting, revert it back, then APPLY all while 360Chrome is closed. It is the Message Box font that 360Chrome uses throughout its GUI. Some portions also use Menu but I haven't tracked down which portions of the GUI use which or if one overrides the other.

The arial black system font is very likely the same issue that verta is having. Not sure if I'll get to another update this weekend or not. The extensions page - I do that intentionally on my copy, I can revert it for the public copy. To me, it is unneeded rarely used clutter that I only bring into view when I do need it. To bring into view, access the Inspect panel, activate the elements tab, search for "action-links" until you get to a <div class="action-links">, highlight that line, then uncheck the "display: none" in the styles section.

Do you only have the default 62 fonts that come with XP or do you have additional or reduced set? http://thundercloud.net/infoave/premium/tips/xpfonts.htm

My letter M does not get smushed, even with your theme. However, your theme does highlight a very minor difference in letter C and letter P that should be enough for me to track down why this is happening. If my letter M looked like your smushed M, I would have abandoned 360Chrome a long time ago, lol.

I've not witnessed either. Others have reported brightness differences. I have a screencap program that shows the RGB color under the cursor and I have been unable to replicate/confirm brightness differences. I've not tweaked any color palette profiles and use un-hacked graphics drivers. Not the latest-and-greatest driver, just whatever I started using when originally installed the computers over a DECADE ago. Several reinstalls since, of course, but always with the drivers I've been using for over a decade. None of my computers are newer than 8yrs old or so.

It somehow depends on the OS and the fonts installed on that OS. For my XP x86, XP x64, and Win10 x64 systems, all of my 1030, 2022, 2036, and 2044 builds all look EXACTLY the same on ALL of my XPs and 10s. As far as that goes, my 360Chrome v11, v12, v13, and v13.5 builds all look EXACTLY the same on ALL of my XPs and 10s. My systems do a registry font-replace and I avoid Segoe UI font like the bubonic plague! But @verta's image above is not Segoe UI so I am assuming he is on XP. His image appears to be a combination of a larger than normal 96 DPI setting for XP coupled with a ClearType "fattening" of fonts. I hate ClearType and don't normally test any of my releases on any ClearType system config. I'm at a loss at the moment. All of my v11, v12, v13, and v13.5, several builds of each, all look exactly identical on all of my XPs and Win10s.

Are you on XP or 10? If XP, can you send me your .theme file?

Download links now included in first post of this thread. Note that even though 360Chrome remains my primary browser even on my Win10 computers, I still use the XP skin. Users that create their own skins or revert to original Chinese skins are of course welcome to do so, it is YOUR computer - it should be disclosed when asking for assistance if your version has been modified.

Unable to replicate here. My monitors turn off when they are supposed to even with 360Chrome in the foreground. They also turn off even if a video is playing, more modern browsers do not.

Correct.

Thanks. Interestingly, I didn't even see any errors in the console.

Works if you add a "display: none" to that stupid popover that hides the clickable button beneath the popover.