I like the new composer, but at least on my version of Chrome (I don’t know if that’s the issue), I don’t see the list of categories when I click the menu:
Due to my computer being a MacBook Pro from 2012, the version of Chrome I can use is this: Version 128.0.6613.138 (Official Build) (x86_64)
I understand that things need to move forward, but if this is the issue, it’s a bit “alarming” for me that first the mobile version on an old iPhone started looking bad, and now things start breaking on old versions of Chrome?
I just noticed that when I click to add tags, nothing happens either. Not on the field, not on the icon.
Since I’m stuck to the Product Support category without being able to change it, I don’t know if that’s the issue, meaning, if there’s no available tags in that category? I don’t think that’s it, because I believe there are tags that are available in all categories?
In case you want to post something that isn’t Product Support before this is fixed, you could visit that category and use the “New Topic” button. In categories where you are allowed to post, this pre-fills the composer with the current category.
Editing the category and tags using topic edit might work too as a workaround.
Got some sort of repro, not exactly the same but assuming something along these lines happens for you too (as in, it’s somewhere in the DOM but at the wrong position – it seems to depend on the size of your composer)
That was in March 2025, and we were just describing which versions of Chrome supported the particular features related to that announcement (relative color syntax, subgrid, etc.). It was not a promise to support Chrome 119.
Our official policy is that we only support the latest version of evergreen browsers (Chrome/Firefox/etc.). Google’s support for Chrome 128 ended in September 2024, so I’m afraid we cannot support it forever.
I’ll look at whether we can update our ‘old-browser’ feature-detection so that a warning banner appears. That will help to avoid this kind of confusion in future.
That is frustrating! Perhaps you could consider switching to Firefox? It looks like their latest version still supports macOS 10.15. That would be much more secure, and would allow you to use websites which rely on modern browser features.
I’ve tracked this down, and it’s a rendering difference in older Chrome versions rather than a bug in the composer.
Details if you're interested
The redesigned composer uses a CSS container query, so the footer adapts to the composer’s own width instead of the window’s. When container queries first shipped, the spec said this also applied layout containment to the element. One effect of layout containment is that fixed-position elements inside it are placed relative to that element instead of the browser window, which is what you are seeing. The spec has since dropped that (thankfully), and current Chrome no longer does it, but older versions such as Chrome 128 still do…
Now, the only way to fix this is to revert to older mechanisms of responsive design, which will make everyone else’s experience worse as trade-off to make it work again in a browser, for which Google dropped support, as David said.
I understand the annoying position you’re in right now, but I’m sorry to say we can’t provide a fix for it.
However, since it’s a CSS issue, you could add custom CSS overrules via a browser extension like stylus to make it work well for you.