Jump to content

Leaderboard

The search index is currently processing. Leaderboard results may not be complete.

Popular Content

Showing content with the highest reputation on 03/11/2026 in all areas

  1. Eventually I will look into it if no one else on the UXP dev team steps up to try to look into it. I did read last week on the Pale Moon forum that someone was writing a XUL extension that un-nests nested CSS, but I can't find the post right now. Right now my priorities are: * Full ES2023 compliance (eventually 2024/2025 but now ES2023 is priority) * Make Tailwind v4 playground render correctly (this will fix a lot of sites not just sites using Tailwind) * Performance improvements * Make WebRTC actually work with modern services * Fix any other sites that I find that are broken If I am being completely honest with you, I have been a bit frustrated because I have felt that the other UXP developers have prioritized things other than site compatibility, and that those other things they are prioritizing are the wrong things to prioritize. I frequently see forum posts where users are told that the CSS or JS feature a site uses is bad and that the user should email the site asking them not to use those features because they are bad. Users don't and shouldn't have to do that. People don't care about what CSS or JS a site uses, all they care about is that the site they want to use is broken. They'll just go use another browser instead. Due to that I've been learning C++, learning how our JS and CSS engines work, and I'm doing what I can to change that in order to keep UXP/Basilisk/Pale Moon/roytam's forks relevant.
    3 points
  2. I haven't taken a look at how to implement this in our codebase yet, but Mozilla's implementation is written in Rust unfortunately so we will have to do a new implementation from scratch. Happy to work together with you to get an implementation figured out, you need this for your XP builds just as much as we do upstream. I have no idea if Moonchild Productions is just Moonchild or if there are other UXP/Pale Moon contributors involved in Moonchild Productions as well. I've never asked. In my case, Basilisk Development Team is just me because nobody else seems to be interested in contributing to Basilisk outside of the occasional PRs from other UXP developers to ensure breakages don't occur after UXP updates.
    2 points
  3. Yesssssa now everything is ready on this cool 10 Watt (even with prime95) board N100DC-ITX. For the very first time I succeed to change entries in Bios menu, so that after the mod they work in Bios. I do not make any mistake in Bios mod, just forget 4 changes from an above layer of setup.bin Dietmar EDIT: The Onboard Graphic (inside the cpu N100) can only work in UEFI mode. So, when CSM is enabled, the Onboard Graphic stops working! I use for this for CSM Enabled the legacy Nvidia GT 730, in PCIe slot. All switches are valid in this Bios. With CSM is disabled via Bios, you have from the onboard GPU VGA graphic and also onboard HDMI. Here is this for CSM modded Bios for the N100DC-ITX, it is a mod of Bios version 1.06. In "Default" settings of the Bios (CMOS reset), CSM is enabled. So, when you do a CMOS reset, after this reset CSM is ENABLED. https://www.upload.ee/files/19149593/bios4.rom.html
    2 points
  4. Yes this will get implemented in UXP at some point but I don't know how to implement it yet. It's not like I can snap my fingers and UXP magically has support for it. It takes time to research, implement, test, and verify there are no regressions or crashes as a result of that implementation. That implementation affects the CSS parser so it will literally affect how UXP reads the CSS for every single site on the web. Even if we had an implementation it would take A LOT of testing before we'd feel comfortable merging it in.
    1 point
  5. I think you misunderstood something here. Web compatibility is my number one priority right now. I already said that earlier in the thread. Basilisk does not, and will never, require AVX for release builds.
    1 point
  6. An useragent override should work. try e.g.: general.useragent.override.distrowatch.com Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:133.0) Gecko/20100101 Firefox/133.0
    1 point
  7. Google's AI does suggest that IDM is known to break FDM: The "official uninstallation instructions" link: https://www.internetdownloadmanager.com/register/new_faq/functions7.html
    1 point
  8. Antivirus programs are INFAMOUS for this type of uninstall "shadow" corruption. Avast, McAfee, Norton, etc all release their own "uninstall TOOLS", because you can't just uninstall them via normal means. And not even "Revo" can solve those uninstalls, you really have to use the developer's "tool" to properly uninstall. ie, does IDM have an "uninstall TOOL"?
    1 point
  9. ... Hence my previous comment you quoted : ... and I was strictly referring to "Moonchild Productions", are you officially part of that team now? Joking here , of course, but my comment was made on Feb 22nd, your fix landed on the official UXP repo on Mar 10th (and has yet to land on a roytam1-compiled binary), so yes, I wouldn't have survived had I held my breath... Jokes aside, my contribution was just to identify the missing JS feature; the report was made here by a UXP-fork user (on an unsupported OS), so the proper way to tackle that would've been: 1. Get access to a machine with an official UXP sanctioned OS 2. Get hold of official UXP-based browser binary/binaries 3. Reproduce the "bug" (rather the platform's deficiency) there 4. Register an account in the official PM forum 5. Report the problem in their WebCompat subforum (few fork users on XP/Vista can/are willing to go through the above ...) ... and then hope one member of the under-staffed MCP team takes it upon themselves to attempt a "fix"; given that the problem, as reported, affected a Polish government web site (relevant probably only to Polish citizens), MCP staff would have little incentive to spend time on fixing that, when other major/more popular sites are broken... So yes, over the years, I've become somewhat pessimistic ... Thanks again for implementing "object.GroupBy" . Regards.
    1 point
  10. I tried the “i219P0” and “XPSP3moreDevicesInf” LAN driver versions on the Asus Prime Q370M-C_CSM board, which has the i219-LM (DEV 15BB) chipset. Both work correctly: To disable the ME on that board, it was not possible to apply the procedure that works for the AIMB-786 board because the text file obtained did not contain the “Setup Item Hidden” option or any other similar entry. Fortunately, the Q370M-C_CSM board allows you to disable the ME function by connecting two pins on the specific header. I also tried the “RTL8125allbest” driver on the asus Prime Z790-P WIFI D4 card. It works even if the duration is not calculated:
    1 point
  11. It doesn't seem to be this SP3 patch. I suppose in hindsight I would say that it can't be. Because that would mean that FDM would work in SP2 but would not work in SP3.
    1 point
×
×
  • Create New...