Oh yeah that was an actual bug. Let me deploy latest here. Sorry about that.
Working now. Hooray!
This has been improved, instead of a meaningless “restore” up chevron – which you could already accomplish by clicking anywhere on the bar – there’s now an X when minimized.
We also show the topic you are replying to specifically rather than the generic “draft in progress” text – as you navigate elsewhere you can see which topic you were actually replying to in the minimized editor.
This has been probably asked and answer, but why do some articles pull the headline and etc. and others are stuck with just the text / hyperlink?
Depends if the target site supports OpenGraph or oEmbed.
I’m guessing there’s not a way for me to know that until I just try it?
There is now, try it.
The last update you guys did 2-3 days ago has caused quoting replies to only keep the first word on mobile, for instance:
I can’t repro that on Android or IOS? Can you list step by step. Browser version, OS version?
iOS 10.1.1 w Safari on iPad Air 2.
That’s not a mobile system, so it gets the desktop version. Haven’t noticed that myself and I use my iPad Pro XTREME XTRA LARGE EDITION extensively with Discourse here and elsewhere.
Question… how do I search within a page using discourse? CTL-F activates the site search, but if on for example the Game Frame Game master list I want to see who used a particular game, the site search isn’t all that useful.
Check the search within the topic checkbox in the search pop up.
Or hit ctrl-f a second time to instantiate normal browser page search function
In topic search with @username should work. That means you are searching that topic, that user.
(Apologies if this has already been discussed. Couldn’t find anywhere.)
I just posted for the first time from my iPhone 5s/iOS 10.2/Chrome and man was that frustrating. Once what I’ve written goes beyond the middle of the screen where the system keyboard starts, I can’t see what I’m typing and can’t scroll down. Well, I can scroll but it won’t stay there. Since I’m at that point now, I’m going to wrap up this post and just hope it’s clear what the problem is.
We only support the official browsers on Android and iOS. Unfortunately “Chrome” on iOS is quirktown central, exhibiting many bizarre behaviors that appear nowhere in Chrome for Android (or Desktop for that matter). Because it isn’t Chrome.
That is slightly changed in 2016 as the faster Safari JS intervals are exposed to iOS apps at last, but the money quote is this, and is true as it ever was:
On iOS, Apple has never allowed third-party browsing engines. Developers can build browsers, but they’re always just wrappers for the platform’s Webkit-based first-party engine.
You were definitely on the mobile layout? You hadn’t accidentally switched to desktop layout somehow?