Content Type
Profiles
Forums
Events
Posts posted by Dave-H
-
-
59 minutes ago, Dixel said:
uBlock has quite some settings to prevent Chrome's malicious behaviour, for example - block remote fonts, CSP reports, disable pre-fetching (to prevent any connection for blocked network requests), disable hyperlink auditing, etc.
I've had a look just in case it was stopping web fonts from downloading and causing the issue on the Digital Spy forums.
That option is switched off though.
0 -
Absolutely right, I can't imagine that it's something that I would ever actually want to use!
I was just a bit puzzled as to what uBlock had to do with it.
Is it something that uBlock would block as a matter of course, regardless of its settings?
0 -
-
Thanks.
0 -
15 hours ago, NotHereToPlayGames said:
If it's a site you use all the time, a simple css replacement in something like Stylus is a very easy solution.
Funny you should say that!
The mention of Stylus jogged my memory that I was already doing exactly that on 360Chrome, and have been doing so for well over a year!
Strangely though, if I switch off Stylus now the Digital Spy forum site still looks OK, so they've obviously changed something.I've tried installing Stylus on Thorium, and importing the Stylus settings from 360Chrome, but it doesn't work, the font is still wrong.
I've attached my Stylus settings file, do you think it's still correct?
The site still looks correct in Supermium without Stylus even installed.
stylus-2024-04-23.json0 -
Thanks, I'll check that out.
I can put up with the wrong font on sites occasionally, but it's annoying when it happens on a site you use all the time!
0 -
Back on topic please!
0 -
Back on topic, has anyone else using Thorium noticed it sometimes not loading web fonts?
I've noticed it on this forum site which I use a lot - https://forums.digitalspy.com/
It looks fine in 360Chrome and Supermium, but not in Thorium, where it falls back to Times New Roman.
The console shows many entries saying "OTS parsing error: Unable to instantiate font face from font data."
I assume this is the cause.
1 -
Absolutely right, certainly in my case!
1 -
17 hours ago, VistaLover said:
@Ben Markson & @roytam1 :
Although what I'll bring up concerns a different browser engine (360EEv13, based on Chromium 86), perhaps the time discrepancy is attributed to a Windows XP quirk/bug, especially if you take into account that upstream codebases (UXP by MCP, Chromium 86) were never meant to be run under Windows XP ...
In the autumn of 2022, our dear @Dave-H complained about 01:00 discrepancies in the timestamps of the history entries of his 360EEv13 profile under XP, when the UK observes BST (UTC+01:00); this issue doesn't manifest itself when the same profile is launched under his Win10 partition; mitigation of the issue, though, under XP involved unchecking the "Automatically adjust clock for DST" control panel setting and manually selecting a region with a [UTC+01:00] timezone for the duration BST is being observed ; you can read the exchange between me and Dave by going to
and do read some posts after that (and the previous page, too, if you don't mind ) ...
Best regards !
Just to clarify, I have never run 360Chrome on the Windows 10 side of my machine, I've never had any reason to!
The history problem was not just the hour's discrepancy in the times displayed, which I could have just lived with, it was the fact that history items from earlier in the current day were not displayed at all.
0 -
I agree about that, I don't like the scrolling single bookmark lists either.
0 -
20 hours ago, ED_Sln said:
@Dave-H
Thorium has the setting you need, in chrome://flags #close-window-with-last-tab toggle to "Never" and the browser will no longer shut down when you close the last tab.
Thank you so much, that's great!
Perhaps rather strangely as it's superficially so similar, that option does not seem to exist in Supermium.
1 -
Please don't ask about things only related to Thorium in this thread, which is about Supermium.
There is a dedicated thread for Thorium.
1 -
Not now, certainly, even though they probably started from the same base.
They are diverging, as these things always do with different developers working on them.
0 -
4 hours ago, hidao said:
It's a bug ,I told to the developer some days ago
Again off-topic, but the faulty file open dialogue has been fixed on the latest version of Thorium, so I guess Supermium will not be far behind!
3 -
The new 122.0.6261.168 version of Thorium seems to be working fine.
One thing I have found is that it generated a folder in my profile folder called 'Screen_AI'.
This appears to be a Google AI thing which it presumably downloaded in the background.Unfortunately, whatever it is, it doesn't work on XP, just generating errors in my Windows System event log whenever Thorium is started.
Looking at other Chrome browsers, there should be an option in the settings to switch off this AI stuff, but that option is not there in Thorium, and I can't find any relevant flags to disable it either. I have worked around it by simply disabling chrome_screen_ai.dll by re-naming it.
2 -
Less memory usage problems certainly, but the jury's out as far as I'm concerned at the moment.
1 -
Yes, there's now a thread about it.
0 -
1 hour ago, hidao said:
It's a bug ,I told to the developer some days ago
FWIW it's the same in Thorium, perhaps not surprisingly!
0 -
1 hour ago, XPerceniol said:
^HI Dave - I am also giving it a try but were you able to get Thorium to pick up your 360 profile? Maybe there is something I'm not getting because I didn't run into this with Supermium. Will try again this weekend when I have more time because tomorrow I have too many appointments. If I have to build a profile from scratch that isn't a huge deal-breaker for me, but I took so much time to get 360 where I want it and will likely not give up on it completely either but its starting to show its age.
Well all my operating systems are on 'bare metal' and I hope they always will be!
I didn't actually import my 360Chrome profile into Thorium.
I imported it into Supermium, and then imported the Supermium profile into Thorium!
As Thorium and Supermium are so similar, I thought that was the best way to do it.
I can't think of any reason why a 360Chrome profile wouldn't work directly in Thorium though.
2 -
OK, I'm giving Thorium 122.0.6261.158 a try on 32 bit XP.
I still managed to crash an Instagram tab with an 'out of memory' message, but it was a great deal more difficult to do it with Thorium than it is with Supermium!
What seems to happen with Thorium is that as I scroll, the memory use does spiral up, but it gets to a certain point and then drops back again. I can scroll for a long time, and it keeps doing that, but eventually it does crash out. This is unlikely to happen in normal use though I would have thought.
With Supermium, the memory just keeps going up, and it crashes relatively quickly.
In most other respects the browsers seem to be pretty similar, although on one website I use regularly Thorium does not seem to be loading the web fonts, so the displayed font on the page is wrong.
With Supermium, it's fine. Maybe a setting in Thorium? I will have to investigate.
2 -
29 minutes ago, Anbima said:
Yes, the page is displayed, but it is not encrypted.
Ah right.
Just ignore me!
0 -
-
21 minutes ago, ED_Sln said:
Hmm, interesting, the emoticons are different from the ones I have, although the font is the same. But the important thing is that they are displayed. Then maybe that site needs "font awesome", there are several versions of them and each has a set of several fonts.
The developer is aware of this problem and is addressing it.
I think maybe the emoticons look different on your grab to my grab because it says it's a 'Top 100', which presumably is constantly changing?
Good to know that they are aware of the file selection problem.
0
Thorium
in Browsers working on Older NT-Family OSes
Posted
Just to illustrate, this is what I'm seeing with Supermium, and 360Chrome -
And this is what I'm seeing in Thorium -
As you can see, the font is completely different.
Looks like Time New Roman to me, but might not be from what @NotHereToPlayGames said!