Jump to content

Mima

Member
  • Posts

    11
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Philippines

About Mima

Profile Information

  • OS
    Windows 11

Recent Profile Visitors

366 profile views

Mima's Achievements

2

Reputation

  1. Upstream implementation pending at https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2244
  2. You can't really be sure about that, as we don't really have enough details to come to the conclusion that it's a regression caused by the platform updates. Anyway, last workaround I can think of: try disabling WebComponents by setting dom.webcomponents.enabled to false via about:config. We've enabled WC by default since March because most of it is working, but the implementation is still not a full 100% complete (more like 95% right now) If that works, then that would mean the website has a pretty poor fallback when the browser doesn't 100% support the WebComponents package, which isn't good practice.
  3. Well that wasn't much help for me either. I can't see anything obvious that would cause the page to go blank like that. There are some familiar errors like min() and unprefixed user-select not being recognized (as UXP doesn't support them yet) and therefore dropped, but they really shouldn't break the page (and those errors appear while logged out anyway, so most likely irrelevant)... Anyway you did try testing in a fresh profile, right? Otherwise your only option might just be to contact the webmaster about it since I can't really reproduce it (I don't have an account) here in my trunk build of Pale Moon, so I can't provide much help than this I'm afraid.
  4. Gmail itself probably got updated and the cache is causing conflicts, which is probably why the bug no longer happens for you after bypassing the cache. It happens. :P
  5. NM doesn't have devtools? Does Ctrl-Shift-J do anything? Does the Developer Tools submenu show up from the Tools menu of the menubar? I don't think there's anything remotely relevant here other than the error at the very bottom... And even that doesn't seem relevant because it shows up for me too while logged out. Btw when I said "find relevant errors", I mean find those which come from the website's code itself, like the jquery error shown in the screenshot. NS_ERROR_CONSOLE errors are mostly irrelevant as they're just errors related to internal browser code of New Moon itself. Same goes with the browser.xul warnings and l10n.js error. Can you try enabling layout.css.report_errors from about:config, clear the console output, and refresh the page while logged in to that dashboard? I'm suspecting this issue has more to do with CSS than JavaScript. It will probably produce a lot more output than before though (which is why this about:config option is disabled by default).
  6. You only need to copy the relevant errors from the console. If the same error repeats over and over, then don't copy them all; just copy a single instance of it and tell us that that error is repeating. Another pro-tip is that most of the warnings (like the CSP errors marked as warnings) you see is mostly irrelevant and can be ignored. You can do that, but I think this forum software should support "spoiler" tags which should automatically hide the contents of the console output you've pasted. Put it within a code block for better readability and nest it within a spoiler tag for best results. Please don't. That's bad netiquette. Btw, you can access the "F12 Browser Console" with the F12 key, which will toggle the developer tools at the bottom of your browser. Not sure why you didn't get that from the very start...
  7. Have you actually tested beyond the "Disney's Oceans" video in https://videojs.com/advanced? Because only that and the MP4 version of Elephant's Dream work in Pale Moon and Edge. The rest don't play for me.
  8. It's the browser console from the developer tools. What's the output from the Toolkit Error Console?
  9. silverni, can you provide the output from either the Toolkit Error Console or F12 Browser Console? Don't forget to clear any output before reloading the page.
  10. It is indeed a VideoJS issue. I've tried Mercury (fork of Firefox 112), Waterfox, Edge, and Thorium; all of them don't play the forest video.
×
×
  • Create New...