Problems with discussion fedoraproject.org website in Brave and Firefox

Site Help & Feedback
1

Hi, I am typing this on my phone so a short story.
Since this morning I can not use the buttons at the top of the home page of the Fedora discussion site (log in, sign up, etc) on both browsers.
I restored the settings file in ~/.var/app for both but did not help. I re-installed both browsers but also no luck. In Firefox I am still logged in, but can’t create a new thread, in Brave I can not log in. This only happens at the discussion webpage. The discuss.kde.org works fine.
What is different in the Fedora page which doesn’t work together with whatever is going on in my Kinoite?

I just did a rollback to 20250205, didn’t help.
I renamed com.brave.Browser and started Brave totally new, did not help.
What can be wrong here?

4 Likes
2

Similar for me. From the Firefox console logs, it seems like there’s a bug in the Discourse JS preventing it from adding some event listeners (which would tie in with the “New Topic” button not working). But then it can’t be all event listeners, because other buttons like “Reply” still work.

Uncaught (in promise) TypeError: can't access property "addEventListener", s is null
    Ember 61
        didInsertElement
        didInsertElement
        i
        _trigger
        i
        _trigger
        i
        didCreate
        commit
        commit
        eX
        _renderRoots
        _renderRootsTransaction
        _renderRoot
        _appendDefinition
        appendOutletView
        invoke
        flush
        flush
        _end
        _boundAutorunEnd
        promise callback*59017/r/<
        flush
        _scheduleAutorun
        _end
        _boundAutorunEnd
        promise callback*59017/r/<
        flush
        _scheduleAutorun
        _end
        _boundAutorunEnd
        promise callback*59017/r/<
        flush
        _scheduleAutorun
        _end
        _boundAutorunEnd
        promise callback*59017/r/<
        flush
        _scheduleAutorun
        _end
        _boundAutorunEnd
        promise callback*59017/r/<
        flush
        _scheduleAutorun
        _end
        _boundAutorunEnd
        promise callback*59017/r/<
        flush
        _scheduleAutorun
        _end
        _boundAutorunEnd
        promise callback*59017/r/<
        flush
        _scheduleAutorun
        _ensureInstance
        schedule
        f
        waitForDOMReady
        init
        _
        create
    <anonymous> start-app.js:17
    async* discourse-boot.js:13
    <anonymous> discourse-boot.js:1

I also see these messages in the console when the page loads:

DEPRECATION NOTICE: Accessing `site.mobileView` or `site.desktopView` during the site initialization can lead to errors and inconsistencies when the browser window is resized. Please move these checks to a component, transformer, or API callback that executes during page rendering. [deprecated since Discourse 3.5.0.beta9-dev] [deprecation id: discourse.static-viewport-initialization] [info: https://meta.discourse.org/t/367810]

DEPRECATION: [THEME 59 'Admin Warnings'] Importing `inject` from `@ember/service` is deprecated. Please import `service` instead. [deprecation id: importing-inject-from-ember-service] This will be removed in ember-source 7.0.0. See https://deprecations.emberjs.com/id/importing-inject-from-ember-service for more details.

Like you, I don’t get any of the same messages on KDE’s Discourse.

2 Likes
3

Thank you @pg-tips, so it’s not in my setup? Then we just have to wait, I guess, or do you have an address where to file a bug report?

4

Perhaps move this topic to “Site Help and Feedback”, and/or create a ticket for Fedora Infrastructure ?

5

Can I, as a level 2 participant, move threads? I have never done that and to be honest I have no idea how to do it.

6

As the thread creator you should be able to change the category and tags… click the pen icon next to the thread title?

9

Yes, that worked.

1 Like
10

Yep, same problem for me on two computers using Firefox.
I was just about to ask the same question.
It was working 8 hours ago.

11

It is working properly again now.

12

Still happening for me, but only sporadically… not sure why it isn’t deterministic!

13

I spoke too soon - it’s broken again!

2 Likes
14

For you maybe, but here the buttons don’t work yet.

15

I guess we should loop in an admin such as @mattdm or @kevin

16

I have the same issue using Chrome.I disabled ad block and I logged in but tried again and no luck.The same with Firefox.I tried to reply to this topic and after maybe 5 tries I was able to log in.So I ruled out it is ad block in Chrome or ublock in Firefox.

1 Like
17

I can create new topics with firefox-147.0.2-1.fc43.x86_64, by which I mean the new topic dialog appears for me to fill in details.

Is this an issue with the flatpak firefox?

18

I’m on regular Firefox. I haven’t updated in two weeks (on this PC) and I updated last night (on my laptop) and the problem is on both devices.

I’m sure this is a Discord issue, not a browser issue.

A curiosity: if I ‘open in new tab’ the buttons work in the new tab, but not the original. However, ‘new topic’ is not working at all.

19

discord != discuss

1 Like
20

Did you have the exact Firefox RPM version, firefox-147.0.2-1.fc43.x86_64, that I reported works?

If you create a new Firefox profile do you still have the issue?

21

Discourse :grinning_face:

1 Like
22

I use Firefox 147.0.3 Flathub Flatpak and Brave 1.86.148 Flathub Flatpak and I have problems with both browsers. I guess it is not a browser issue, I mean Firefox and Brave are 2 different browsers, so what is the chance they both have the same issue at the same?