This is not OK at all whatsoever
-
So I've always been using discourse on desktop mode on my phone. Now they've killed it entirely:
This. Is. Not. OK.
-
So I've never used Discodesktop on mobile, so I don't know how it worked before, but what's the issue? It goes off the screen at the bottom? Something else?
-
Something else?
YOU CAN NOT SCROLL IT!!!!!!!!!!!!!!!!!!!!!
And I had to make that topic in mobile mode because the CATEGORY SELECTOR WAS OFFSCREEN ON MOBILE DESKTOP!!!!!!
-
@loopback0 said:
Something else?
YOU CAN NOT SCROLL IT!!!!!!!!!!!!!!!!!!!!!
Ah gotcha. I assumed the scrollbar had hidden itself, rather than it didn't exist.
-
YOU CAN NOT SCROLL IT!!!!!!!!!!!!!!!!!!!!!
Which is amusing, because the hamburger menu which is seemingly always "too tall" does scroll for me (at least, on Chrome for Android).
I don't have enough notifications to test that scrolling.
-
# YOU CAN NOT SCROLL IT!!!!!!!!!!!!!!!!!!!!!
And I had to make that topic in mobile mode because
**CATEGORY SELECTOR WAS OFFSCREEN ON MOBILE DESKTOP!!!!!!**
This is how my inner monologue read your post.
-
If you will recall, desktop on mobile is not supported:
Zerobox left out the money quote:
@codlnghorror said:
I personally don't see the issue, other than a f**ked up desktop display on mobile, which is Not Our Problem.
-
not supported
I know.
I kept landscaping my phone to dismiss modal popups. But at least it tried to work.Now it's done. over. dead. game over.
-
And feature parity? FORGET IT!!!!!
-
desktop on mobile is not supported:
But Mobile Discourse gives you a fucking link.
It's another feature that it lets you use despite it not actually being Jeff supported so it just shits all over you when you use it.I don't know why we fucking updated. Now we get the stupid but without any chance whatsoever of doing anything about it.
-
YOU CAN NOT SCROLL IT!!!!!!!!!!!!!!!!!!!!!
I don't even have notifications at all, and I'm ON A DESKTOP. ?
-
-
Now it's done. over. dead. game over.
I was going to give it a whirl to see if there could be some custom CSS to put in to make the New Topic editor work on both Desktop on Desktop and Desktop on Mobile, but the way they have it laid out means to get it to work for Desktop on Mobile will completely screw up Desktop on Desktop.
The big thing I saw while trying though is they put a
min-width: 1280px
on the editor container on Desktop view, no matter the actual screen resolution.
-
The big thing I saw while trying though is they put a min-width: 1280px on the editor container on Desktop view, no matter the actual screen resolution.
... they really did. WHY?!
-
they put a min-width: 1280px on the editor container on Desktop view, no matter the actual screen resolution.
Why the fuck?!
Oh, yeah, JeffCo™.
-
There is no mobile desktop, it's desktop mode on mobile. (And it's NEVER worked.)
-
they put a min-width: 1280px on the editor container on Desktop view
That's weird; I don't see... Oh, it seems to be only the container, not the editor itself; that's properly sized for my window. Fortunately, because it would be even stupider if that were too wide to fit.
-
On an unrelated note, there's a deprecation warning from ember in the console. Has that always been there, or is it new in this update?
-
it seems to be only the container
Hence why I said:
on the editor container
But, to be honest, I see no reason to have a min-width on a block level element unless the child elements are too wide (which they aren't/shouldn't be) and don't want it to scroll (which it shouldn't anyways, and that's what the overflow rules are for).
-
But, to be honest, I see no reason to have a min-width on a block level element...
Discompetence.
-
Discompetence.
(Reply to post 20; jellypotato to post 1. Yay.)
Is that in the Discopædia, yet? If not, get thee hence.
-
Discompetence
10/10 Needs to go in the Discopædia.
'd because I couldn't copy/paste 'æ' fast enough...
-
I'll find out, and handle accordingly.
-
I couldn't copy/paste 'æ' fast enough.
Alt+0230
I don't have that one memorized yet, but I always have charmap.exe open to look stuff up quickly.
-
@NedFodder said:
I couldn't copy/paste 'æ' fast enough.
Alt+0230
I don't have that one memorized yet, but I always have charmap.exe open to look stuff up quickly.AltGr+AE
-
LOOK WHAT ELSE THEY BROKE.
(those caps were an accident but I'm not fixing it)
-
-
jellypotato
Which will never be fixed, because it would require one iota of debugging skill. Much better to keep putting fresh lipstick on the corpse.
At least the Discodevs should be happier over at echchamber.d now they don't have to deal with actual bug reports.
-
AltGr
No repro. No AltGr key. Alleged AltGr emulation with Ctrl+Alt doesn't work. Changed keyboard layout from EN-US to EN-international; still no joy. If there's a way to do this without buying a new keyboard, I'd love to know about it.
-
They're still getting a decent amount, not considering the ones that got Jeffholed.
-
Meanwhile over at mobile on mobile (as if that's even a supported configuration), in landscape mode I can see all of five latest notifications at once now, which is like half of what you used to be able to see.
Is there a word which means "incompetence so strong that it's indistinguishable from actual malice"? There should be. Discomalpetance. There.
-
German T2 layout - the one everyone secretly wishes they had:
AltGrD,A
-
-
æ
æ
-
suckers!
Spanish layout: Alt Gr + a = æ
-
æ
æ
Well, yes, there is that, but AltGr is easier, if it works, and even Alt+#### is easier for the symbols that have that combo. Plus, they work in non-HTML/non-XML documents, but entities don't.
-
@abarker said:
AltGr+AE
áé
CNR.
æ
WOMM
To get the characters you indicated I have to do AltGr+A' and AltGr+E', respectively. Must be different mappings.
-
@abarker said:
AltGr
No repro. No AltGr key. Alleged AltGr emulation with Ctrl+Alt doesn't work. Changed keyboard layout from EN-US to EN-international; still no joy. If there's a way to do this without buying a new keyboard, I'd love to know about it.
On Windows systems, WinCompose does a decent job.
-
And feature parity? FORGET IT!!!!!
Well, they're already trying to remove the composer buttons, so who knows, maybe we'll get to feature parity eventually.
Filed under: you expected what, implementing features?
-
Poking around in settings, I see this:
How did you switch to the full site before? We lost our CSS theme selector due to breakage. Maybe we're breaking the ability to switch back? Maybe they just forgot to update the admin option? Who knows?
-
I was going to give it a whirl to see if there could be some custom CSS to put in to make the New Topic editor work on both Desktop on Desktop and Desktop on Mobile, but the way they have it laid out means to get it to work for Desktop on Mobile will completely screw up Desktop on Desktop.
I tried making it scroll using some buttons, some JS, absolute positioning and messing with the
left
property, but they made such a mess of the DOM even getting it to properly display withoverflow-x: hidden;
was damned near impossible.I'd assume they broke it even more by now.
-
How did you switch to the full site before?
The hamburger menu shows "Desktop View" on mobile devices instead of "Keyboard Shortcuts".
-
-
How did you switch to the full site before?
Personally I used a desktop browser agent because the web is completely broken if you tell sites you're mobile (why yes, I wanted to see the first page of your mobile site instead of the article I clicked on, or only have 5 lines of huge text per screen on a sodding phablet).
-
I hate the creep message that appears blow the thread so much.
-
-
@HardwareGeek said:
If there's a way to [have a compose key] without buying a new keyboard, I'd love to know about it.
On Windows systems, WinCompose does a decent job.
... which can be found (after clicking through to the GitHub repository) at http://wincompose.info/
Finally you can make the Menu key do something useful
-
Finally you can make the Menu key do something useful
Do you mean the Application key? Bring up a contect menu on the elemt with keyboard focus? I use that all the time!
-
ew.
Now, now, we all touch ourselves at times.
And I've said it before - you've had 4 icons, one of them was a common and obvious metaphor for notifications, one was search which pretty much had to stay that way, one was the hamburger that held about half the settings and otherwise quick links, and the last was the profile icon which held the other half.
And instead of merging #3 and #4, they merged #1 and #4, so now we have notifications lumped with that other half of settings under a non-obvious icon, and an incomplete hamburger.