NotHereToPlayGames

I still plan on creating a dark theme - but it's so back-burner that it's sitting on the stove at the appliance store instead of the stove in my own kitchen.

For those truly curious as to whether "dark themes" are 'better' for your eyesight -- https://www.androidauthority.com/dark-mode-1046425/ https://www.maketecheasier.com/are-dark-themes-better-for-eyes-battery/ "In terms of readability, the verdict is clear: black text on a white background is the best." Um, no duh in my view, you cannot buy a book or a newspaper that uses white text on black paper -- Q.E.D. But for any of you entrepreneurial type dark-theme fans that feel so strongly that dark themes are the best invention ever, maybe you can found your own company speciallizing in books and magazines using "dark theme" print schemes - "good luck". I also had Lasik several years back and also corrected an astigmatism so this too could explain why DARK THEMES look TERRIBLE per MY eyesight. Couldn't resist...

I do not use this option and have no issues with pop-ups without it - I only allow whitelisted javascript and do not use any pop-up blockers be they built-in or be they extensions. I personally find that pop-up blockers are a headache 70% of the time while blocking ALL javascript then reloading a webpage that simply "forces" javascript is only a headache 30% of the time. I will take that 30% over that 70% any day of the week To each their own... Aware, have not gotten this far yet, this should be resolved once alpha finally makes it to an official "rebuild_1". Blah, blah, blah... I'm starting to feel like "dark themes" have somehow become the ultimate mind-melt control mechanism of "tech giants" indoctrinating the mind and turning us all into "Lemmings" -- sorry, I will not follow those Lemmings over the cliff, I am not a "gamer" and do not see the need for my web browser to look like a scene of some video game so "easy" to the eyes that a "gamer" will spend the entire day in front of it and then wakes up one morning and finally decides to let some sunshine in and finds himself wondering how life passed him by... But I digress...

Thanks. Yeah, profile maintenance can be a bit of a pain when updating frequently. I created an AutoIt script that recreates my profile for me - fully automated, always kinda fun to watch the mouse move around and text fields filled in with no interaction with the mouse or keyboard. I prefer to create a brand new profile from scratch with each and every release, I don't try to preserve it or migrate it, I install extensions from the ground up each and every release.

Download link for v13.5.1030 Alpha_6 added to first post. en-us.pak -> capitalization correction missed in previous alpha's options.zip -> switcher_manage.js search_engine_manager_engine_list.js options.js appstore.js appstore.css cookies_view.css import_or_export_bookmark_overlay.css shortcut.css options_page.css advanced_options.css browser_options_page.css options.html

Technically not a bug. That "feature" ends up being removed/disabled COMPLETELY but all I've done so far is to remove the FILES associated with the "feature" and have also removed the .xml files that go with the popup. I still need to remove the "access points" that tries to execute the files that are now no longer there (and that is why you have a lockup). That is a (known) side effect to having "portions" of that feature not yet removed. While on the topic, it's also why I would discourage using any of my builds (or even Humming Owl's builds) where the end-user tries to "mix and match" files for the sake of something like html5test stability (as an example). Some of the telemetry "components" exists in SEVERAL files. I will be rolling out SEVERAL alpha releases along the way as an attempt to ISOLATE any single set of changes causing html5test instability. I personally suspect that NONE of the changes cause that instability and just by bumping up to v13.5 solved that issue - will know more as we roll out alpha releases. But I do discourage end users mix-matching basically several main "container" files because they contain dozens upon dozens upon dozens of files "inside" that all tie in with each other. When ALL of those "container" files are used TOGETHER, the end user will not (should not) be able to crash their browser by attempting to access something like a NoCoin setting intentionally broken/disabled/removed in dozens of "container" files.

Download link for v13.5.1030 Alpha_5 added to first post. srx/xml updates.

Technically one of the very first changes was to chrome.dll but the only change to that file thus far is to default to English.

Dropbox has always been a bit of a nuisance for me. Have not tested in my v11 but my v12's and my v13's have always had random crashes when using Dropbox - maybe only 10% of the time or so but a crash is a nuisance no matter what the percentage. Good news is that Dropbox has not had any crashes yet on v13.5 -- knock on wood.

Good deal. That file modification also removes a "safemon" user data folder and two "crash reporting" telemetry triggers (credit to @Humming Owl). v13.5 locks up for me every once in a while on FIRST RUN ONLY (only when creating a new profile) but other than that it seems stable.

Download link for v13.5.1030 Alpha_4 added to first post. The only update is the 360chrome.exe file in the Chrome -> Application folder. Should not effect stability but please report if your findings are otherwise.

Download link for v13.5.1030 Alpha_3 added to first post (updated).

Download link for v13.5.1030 Alpha_3 added to first post. Disregard momentarily.

You and popup blockers, unreal, lol.

No skin off my back I will be creating a darker theme one of these days, no sense of urgency on my end. Depending on how much time it takes, I may do a 98/2000-like skin also.

The home button location is defined in Settings -> Basics -> On Startup -> Open Home Page. Even if you don't want to open the home page on startup, it is still defined by the On Startup setting. Oops, I misread your post the first time around. You're wanting the home page to open in the CURRENT tab and not open in a NEW tab.

Seems like something is wrong with the extension not fully disabling. I'd uninstall the extension(s) and try an OLDER version.

I only tested those links in Incognito Mode (no extensions). That's really the only way to rule out that an extension is causing your issues. Also, I thought "polyfill" was why several of the YouTube folks started using a "mobile" link versus the "normal" link?

All three links work for me in 12 1247 r 8. Correction - if r is regular then I should say that all of these open without any errors in 12 1247 u 8 (I only use the "ungoogled"). But I suspect this is an XP x86 XP2 issue and not a regular versus ungoogled issue.

I need an actual link, please. I personally have no clue how to even find links to Twitter content, I've never visited a Twitter link in my entire life - no exaggeration.

I added a citation for our discussions which led to the "ungoogled" modifications.

Added approximate "percent complete" notes to alpha download links in first post to avoid confusion.

Noted, thanks. I do several GUI changes to that window. By default, an incomplete or broken download icon will not be lined up with rows above and below. Or it could be the Pause and Resume icons while a download is still downloading, don't recall offhand. At any rate, didn't get that far yet. If we put a progress bar on what tweaks/modifications have been completed, Alpha_1 was at 2% and Alpha_2 is at 9%. Still a very long way to go to get v13.5 caught up with previous rebuilds. I guess I assumed that was implied when I labeled it "alpha"

The "Use a prediction service" is in the wrong location - it's because file numbers are not indexed the same between v13.0 and v13.5 "Pressing Tab on a webpage" is in the wrong location - file numbers do not index the same from version to version. "This setting is" for the "Extensions" button in the lower left corner is not supposed to say "This setting is" - file numbers do not index the same from version to version. It's not supposed to say "File extensions" above "Use last download directory" - file numbers do not index the same from version to version. You're likely seeing those types of errors all over the place - all due to copying a file intended for v13.0 over to v13.5 -- can't do that.