Problems with discussion fedoraproject.org website in Brave and Firefox

Site Help & Feedback
63 
Uncaught (in promise) TypeError: can't access property "addEventListener", s is null
Ember 21
ember-events.js:214:7

and

Uncaught (in promise) TypeError: can't access property "parentElement", e is null
    removeClickHandler clickable-topic-row.gjs:30
    Ember 7
clickable-topic-row.gjs:30:5

and

Uncaught (in promise) TypeError: can't access property "parentElement", e is null
    removeClickHandler clickable-topic-row.gjs:30
    Ember 14
clickable-topic-row.gjs:30:5

are the JavaScript errors logged by Firefox.

1 Like
64

I have been trying to find the same type of errors @decathorpe sent, but I can’t find them. I looked in the Developer tools but I have no idea what I am seeing. This is so not my cup of tea.

Did something change in the mean time because now the buttons, both in Brave and in Firefox, work here.

65

Buttons work as of writing this reply. Guess discourse people worked their magic.

1 Like
66

On the meta.discourse thread they say:

We tracked it down to a theme component with an event listener that needs to be modernized. That customization has been disabled in the meantime so things should be back to normal.

Sounds like we’re good for now then!

3 Likes
67

Yup, my colleagues found the theme that was causing issues and disabled it.

Sorry you all for the trouble :expressionless: and thank you for using Discourse and being comprehensive :+1:

For the technically inclined / curious

The problem is that the theme-component was using an older strategy for adding event listeners to Ember components. We recently did a round of modernization in Discourse core, which means that the older strategy (adding specially-named functions to the component class) is no longer compatible with the “categories-and-latest-topics” component.

Clearly the error message here wasn’t very useful, and it shouldn’t have caused as many problems as it did. We merged an improvement which will make the error less catastrophic, and make it easier to identify/fix.

The reason it appeared sporadic is that the error was only triggered on the /categories page. But once you’d visited that page, the app would get into a bad state where various things would stop behaving properly.

5 Likes
68

All the categories use a lot of space and I have to scroll a lot. That is why I use uBlock to remove them (on my desktop computer, which not caused the issue). While using Debian on the Mobile computer, I not installed uBlock. So it was really a fight against the Dev-tools which popped up aromatically telling me the method was depreciated. With ESC I could interrupt for a moment but a moment later it started again. I even was thinking that the keyboard had an issue :slight_smile:

Thanks for solving it.

69

@zogstrip Thanks for the quick support :classic_smiley:

1 Like