above post
Aaannnd I just found that the adress bar in fact has the correct link to the post at the tip of the screen. Magic?
So discourse SW has worked around that bug!
Aaannnd I just found that the adress bar in fact has the correct link to the post at the tip of the screen. Magic?
So discourse SW has worked around that bug!
My “workaround” for the blind typing:
Now you are able to see what you type and you can move the already written text up and down…
Remark: this works only in portrait mode, no chance to write in landscape
My workaround so far is Notes app (just write all beforehand and just paste)
My workaround so far is Notes app (just write all beforehand and just paste)
Uh, that sounds so 1990’s…
No problems with newline / carriage returns?
But when I switch to landscape I can see the preview. Handy when you are posting links, oneboxes, quotes…
Oh with quoting/partial quoting it will almost for sure not work, but no issues with crlf from what I’ve seen for now (still hoping 3.4.0 browser update will make it somewhat usable at least, we’ll have to wait and see)
My guess: You’ve performe-d this action too many times, pls wait 1 minute bef-ore searching again? Not sure what else could be rate limited
My guess: You’ve performe-d this action too many times, pls wait 1 minute bef-ore searching again? Not sure what else could be rate limited
Yes!
But which action? I swiped away the browser to read an email and then that popped up.
Oh… No idea then, unless you left the browser on search results and it auto-reloaded it triggering that? If search was not involved really not sure (check url next time, ending could give hints on what went wrong)
Following a hint and trying o delete the full post above.
Please see here
… Interesting to see to be able click onto at top right of an other member’s post, which work if logged in. [Side note: There migth be a better symbol for 'Post's History View', and how many times edited shall not shown]
… As for the even if not logged in, they can be looked up through the deep-link of course need to know the excat name of it, if mistyped one can see this server seems based on OPENRESTY. Anyway.
… At least: Now we know care needed by thr…
for further discussion.
Now quoting above post swithout the third picture attachment link:
And another one of those not readable popups. For all the other I could guess the text by knowing what I did and some words.
But for this one?portrait
landscape
---- to delete below pic, now deleted the picture’s link text
But thar wrongly uploaded pic is still on the server viewable via
https://forum.sailfishos.org/uploads/db4219/original/1X/dbb90920873addab1893c11c837aedc42afdec1a.png
No issues on this site with the current (3.4.0.22) default browser.
The keyboard still overlays the composing window for me, which sucks.
We have an open bug report about that in our internal bug tracker
Thanks for letting us know…
As written above in the edit I would like to know what makes you think this is inappropriate?
Please make use of PM…
You are right. I was using the forum with the Gemini PDA (no virtual keyboard). On my Xperia XA2 the composing window is hidden by the vk when replying to posts (but not when creating new posts)
So, something changed. I guess new version of forum SW?
See log out button gone?.
Minor annoyance but something I hate also in real life web site behavior, change as change is progress and no change is standstill? But moving buttons around or changing name to icon or such stuff is just … imho (do not take this too serious ).
Another thing I noticed is that the buttons in the hamburger menu (Latest, Unread, Badges and so on) inside the native browser in SFOS 3.2 do not work anymore. But only in landscape orientation, in portrait they work as usual!??
The newer browser in SFOS 3.4 does not show this behavior!
(latest) SFOS version 4.1.0.23 EA
and SF browser still cannot let me know what is wrong with trying to post something on this forum. And especially only let me dismiss this popup in landscape mode.
Please see the screenshots (portrait and landscape):
Curious, no fix ideas in last 8 months? This blind typing just isn’t fun anymore, esp. when predictive tezt input isn’t qvqilable on aarch64.
Actually, we do have fix ideas. And I believe there is even a good chance that we will get the fix in the next release.