Jump to content

NotHereToPlayGames

Member
  • Posts

    6,714
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. It could also be that the web site is NOT written correctly! Some headers are supposed to be IN CONJUNCTION with OTHER headers and a lot of web designers tend to forget or overlook that.
  2. No. What you are seeing with that is basically security "rules" changing and header rules being used differently when Chrome v69 (360Chrome v11) was released in late 2018 versus when Chrome v86 (360Chrome v13 and v13.5) was released in late 2020. In the world of web browsers, a LOT can change in two years.
  3. Technically not true. It's because v11 is not able to access the PlutoSans font (see below) and what you are seing in v11 is the "fallback" font (I didn't track down what that is) whereas v13.5 is able to access the PlutoSans font. So of course you are not going to see the same thing when comparing what you see in v11 to what you see in v13.5 - you're not looking at the same font. You can get v11 to access the PlutoSans font by adding this startup command switch --disable-web-security But this will just get your v11 to look like v13.5 as opposed to the opposite direction.
  4. For reference -- https://www.dpd.com/de/de/pickup-paketshops/ font-family: PlutoSansLight / PlutoSansRegular / PlutoSansExtraLight font-weight: 300 Not likely.
  5. Mileage may vary, of course. I myself have never witnessed one driver render subpixel better than another. I'd kind of have to see "before and after" and it should be able to be captured via lossless bitmap. I do have one laptop still on XP but it will likely be Christmas Break before I could do some experimenting on driver versus driver.
  6. My XP was always set to Standard font smoothing, never to ClearType font smoothing. Standard was fine for me, but I did have to BLOCK any-and-all .css anti-alias fonts via Proxomitron, uMatrix, or Stylus, depending on how the web site was configured. Standard was always fine for me so long as I didn't allow web sites to use Roboto, Segoe, Calibri, Consolas. But I also had to disable DirectWrite - one of the reasons that even though Win10 isn't nearly the nightmare that Vista was, I continue to use 360Chrome most of the time even in Win10. Supermium has also returned GDI versus DirectWrite but I cannot bring myself to using a web browser that isn't "ungoogled". Every user will have their pros and cons, their preferences. Web browser selection is always a matter of user preference. I didn't have to switch Standard off or on depending on which programs were running, it was ALWAYS on.
  7. I mean, if you don't have a "before", I wouldn't go out of your way for it. I've recently migrated to Win10 and it does not suffer the NIGHTMARE that I witnessed in Vista. The nightmare haunted me so much that I didn't even try Win7.
  8. Do you have a "before and after" type of pic? I basically "had to" remain on XP when Vista came out - Vista's font rendering was a migraine nightmare I never wish to repeat. I experimented with SEVERAL drivers during my XP Years and I never witnessed any difference - they either "worked" or they "didn't" as far as reaching advertised GPU resolution but no difference in the "dancing" red and green "subpixel" rendering NIGHTMARE. My eye doctor once described it as "the exact opposite of being color blind", that my eyesight can see/detect (and still does decades later) the "subpixel" colors that many people simply do not "see". Do you have a "before" pic that shows the red and green subpixels and the "after" pic showing that the one variable changed (the nVidia driver) being the "fix"?
  9. @Anbima - I totally get the font issue, I really do. Font subpixel rendering literally gives me migraines and I have to resort to several tactics to get fonts on my system to look "right". One add-on won't do it all. One user script won't do it all. One style sheet won't do it all. My four lines of defense are (in this order) - Proxomitron uMatrix Stylus web browser Developer Tools (F12) Sure, we "could" add Tampermonkey to the mix, but it's not really the right tool for the job. While uMatrix is "above" Stylus, it is only in the sense of BLOCKING third-party fonts, I do not use uMatrix to perform what Stylus is better at performing. Proxomitron is the "Swiss Army Knife" of web filtering - but it isn't for everyone and has a steep learning curve. A few of my Proxomitron filters associated with fonts - And you've seen what Stylus can do. But sometimes we need to consider that sometimes we make life more difficult than it needs to be and the web browser's Developer Tools (F12) is really all that is needed. If I visit something like DHL only a dozen or so visit during one month of the year and it's never visited the other ELEVEN months of the year - is a "permanent" solution for DHL really even "needed"? Especially when the web browser's Developer Tools is only a few clicks away and you can change a web pages font rendering "temporarily" within SECONDS as opposed to the HOURS it takes seeking something "permanent" or something "all-encompassing"?
  10. You will NOT find ONE rule that fits EVERYWHERE. I will repeat what I said earlier -- I'm unsure if you are aware of how long the road is that you are about to travel. There are folks that write styles sheets with TWO HUNDRED lines of code that still don't catch "everything". There are folks that write user scripts with TWO HUNDRED lines of code that still don't catch "everything". As far as your latest URL, using body, html, h3, p {font-family: Arial !important;} catches more fonts on that URL, but still not "all". I suppose you could try * {font-family: Arial !important;} (note the WILD-CARD ASTERISK) and see if that is satisfactory.
  11. It's not that "linear". If it takes uBO 400ms to perform what Stylus can do in 200ms and having both only increases RAM by 10 MB but results in saving 200ms a thousand times per day, then that to me is kind of a no-brainer. Every user must weigh their own pros and cons. My hunch is that you have extensions that I view as "worthless". That doesn't make them worthless to you. uBO is obviously FAILING at the task you are asking it to do or we wouldn't be having this discussion.
  12. Stylus is the correct tool for the job. uBlock may be able to "in a limited fashion" but it does not do it as well as Stylus.
  13. The "light turning on" or the "disk spinning" is not one in the same with "files are being scanned". That was my primary point. Those three finds are from very old versions, I grant you that, but they to contain "facts" that files are not being scanned just because the disk spins or the light turns on. At any rate, now it has befallen to which of us is going to get the "last word". I'll let you, as we both know you will reply . As so often is the case here at MSFN, someone says "done" but they actually keep coming back, "my bad". LOL I'm going to blame it on long Holiday Weekend and "boredom".
  14. I use version 1.5.15. Unsure if newer versions are MV3 or MV2. 360Chrome can only use MV2 extensions. I often intentionally user OLDER versions as newer is often just bloated and not as efficient. https://www.crx4chrome.com/crx/45976/ You then need to write a style sheet. I'm unsure if you are aware of how long the road is that you are about to travel. I also style-sheet my Stylus interface, so this will not look the same on your end. This style sheet sets ALL body and html tags on ALL web sites visited to Arial. This will override the "Delivery" font on your DHL example and the "Roboto" font on your everydrop-counts example. If you wanted to apply to only specific web sites, you would add them using the "plus sign" to the right of "Applies to Everything". You may also find that some web sites that you want "Delivery" or "Roboto" changed will have them set in a tag other than body or html. Something like <div> or <span> or the list is endless. There may not be a "one-size fits all" approach and this "fix" could grow quite easily.
  15. It's kind of an "infinite loop" argument, if you ask me. You are correct that no reports exist for official v115. But how much of that is because official v115 does not work on hardware where floppy disks even exist? I've never witnessed this when I did have hardware that did have a floppy disk. I no longer have that hardware. I also no longer run XP (nor do you). What we need, if we truly want accuracy and not heresay, is somebody that has XP and a floppy drive. I did not witness this "bug" when I did have a floppy drive. I fear neither one of us is doing the "argument" ANY justice. So to me, we both win. And we both lose. That's the best I can do for you, lol. Though now I'm kind of curious, would an external DVD Burner have this same "bug"? I do have an external USB-driven DVD Burner.
  16. The FDD light turning on is NOT an indication of "files being scanned". NOR does it have ANYTHING to do with "country of origin". This is PROPAGANDA and MISINFORMATION. I'm done. <dead horse>
  17. Feel free to research before jumping on some bandwagon blaming this to be "from that country" or only after Opera was sold by Norwegians to Asia. Here is Chrome v24 accessing floppy drive -- https://bugs.chromium.org/p/chromium/issues/detail?id=153763 Here is Chrome v26 accessing floppy drive -- https://bugs.chromium.org/p/chromium/issues/detail?id=173953 Here is Chrome v28 accessing floppy drive -- https://bugs.chromium.org/p/chromium/issues/detail?id=234318 This is NOT a "from that country" or "sold to the Asians" CONSPIRACY.
  18. Are you referring to this - https://msfn.org/board/topic/180462-my-browser-builds-part-2/?do=findComment&comment=1187101 ? I don't use dark themes but I'm finding over a hundred .css files inside the ft_deepdark.jar file.
  19. Stylus would be a better route to take than Tampermonkey for this sort of task.
  20. It is here. But that page takes a very VERY long time to load. The userscript doesn't actually replace the font until AFTER it fully loads.
  21. Me thinks 720p shall do just fine. No real fire has a crisp and clear distinction between adjacent shades of orange, yellow, red, or blue. And flames aren't as fast-paced as some action flick on the Big Screen. "This fireplace doesn't look real, I've never seen black backgrounds at the campsight show my reflection like this shiny TV and its crisp color ratio." Hmm, maybe that's it, I want my world to look "real" and not like a cartoon. waka waka waka
  22. // ==UserScript== // @name -- Replace Font // @version 0.1 // @exclude https://www.google.com/* // @exclude https://www.bing.com/* // ==/UserScript== var elementList = document.getElementsByTagName('*'); for (var i = elementList.length - 1; i >= 0; i--) { var elementItem = elementList; var style = getComputedStyle(elementItem, ''); elementItem.style.fontFamily = style.fontFamily.replace(/Tahoma/i, 'Arial'); elementItem.style.fontFamily = style.fontFamily.replace(/Roboto/i, 'Arial'); }
  23. That one plays smooth for me in 1080p (its maximum here in 360Chrome, did not check if it goes higher in other browsers). Even on the ancient Core2 Quad Q6700 with 4GB RAM that I am on at the moment. Well, "smooth" other than the actors acting like they are in zero-gravity. At least it "looked like" actors acting and not real NASA footage (didn't watch the whole thing).
×
×
  • Create New...