Hmm, The URL icon definitely is not broken, as it works perfectly below from a desktop, in this case Chromium, but it also works from Firefox. Here's a link where I used the URL icon:
When I click the URL button, I get a box that displays http:// with buttons for OK and Cancel. Into that box I can paste the address I want to link to.
Then, if I click OK, the address appears in my message but the box doesn't go away. I may be wrong, but I seem to remember that clicking OK used to dismiss the box.
If I repeatedly click OK, the address appears multiple times.
If I click Cancel, nothing happens.
The only way to dismiss the box is to click somewhere within the message itself.
Do you mean the "cancel" button isn't working? If I click anywhere but on the dialogue box for the URL link, it goes away. There remains functionality of the icon to make links. The breakage to which you refer to is a feature not working.
Not working = broken in Miss Amanda's addled brain, but let's not quibble. If Miss Amanda had a lamp that gave off light even though the on/off switch didn't work, the lamp would be broken even though its functionality to shine in the darkness was intact.
The Cancel button does not work -- that is correct.
That's a different issue than mine. Which is the difficulty posting a link using the nice and tidy URL BBCode. I am okay with not using it and posting bare links: i.e. https://www.startpage.com/ rather than Startpage
Something weird is happening with the sizing of the categories box. I'm using an android phone.
The box immediately below the one called 'categories' is called 'recent discussions'...that is the one I am having issues with on my android using Chrome. There is pages and pages of white space to scroll past before I get to the 'recent discussions' link. ....but I suppose it could be the same issue if the categories box is massive. Been happening several days now.
I have had this problem before and I am having again. I was require to sign in. When I clicked Discussions, I was kicked out to a sign in page again. If I went into a forum I remained signed in. I tend to always use Discussions because I am interested in the most recent conversations. Any thoughts on why this is happening and how to remedy it? I am using Firefox on a PC.
Seeing the sign-in page doesn't always mean you need to sign in - if you can see your name and icon below the Shop of Fools trolley, you are already signed in. (On a phone, you'll just see a menu button.)
After being signed out, if I sign back in and go to the "recent discussions" view (my default point of entry), I frequently find it's telling me I'm not signed in. I have to go back and forth to the sign-in page several times before the system will accept me via "recent discussions" view.
I found last time it took a few days to properly sync recent discussions: if I used the back browser button for while it took me back to the last sign in point. (I'm using Edge)
After being signed out, if I sign back in and go to the "recent discussions" view (my default point of entry), I frequently find it's telling me I'm not signed in. I have to go back and forth to the sign-in page several times before the system will accept me via "recent discussions" view.
I've had this a few times and it makes no difference which entry point I use (i.e., I'm signed out, sign back in again, click on anything that might lead to a discussion, and am kicked out a second or third time).
I wasn’t sure whether to add this here or create a new thread.
I’m noticing a changed behaviour on my iPhone. It is irritating and now mimics behaviour I was already seeing in Safari on my laptop.
If I access a thread from ‘Recent discussions’, and then use the back button to go back to the ‘Recent discussions’ page, it initially returns to the place on the page where I left it, but then jumps to the top of the page. It doesn’t matter so much if it is one of the top few threads, but it is pretty irritating if I have been down near the foot of the page and have to scroll all the way down again to find where I was.
Not that this addresses the Ship-side contribution to the problem, but one way to address that annoyance generally - be it the Ship, craigslist, or pornhub - is to open the links in new tabs. That way, when you're done with what you did at the link, the original tab is in the same scrolled-to state that you left it.
I wasn’t sure whether to add this here or create a new thread.
I’m noticing a changed behaviour on my iPhone. It is irritating and now mimics behaviour I was already seeing in Safari on my laptop.
If I access a thread from ‘Recent discussions’, and then use the back button to go back to the ‘Recent discussions’ page, it initially returns to the place on the page where I left it, but then jumps to the top of the page. It doesn’t matter so much if it is one of the top few threads, but it is pretty irritating if I have been down near the foot of the page and have to scroll all the way down again to find where I was.
Safari on my iphone does the same. What is happening is that when you hot the back button, it takes you back to the past state of the page. The page then refreshes, and since it is essentially a new page, it takes you to the top.*
It began happening after the most recent upgrade to the iOS that I did, 13.4. SO there is something new in Safari that interacts with the ship software differently than before.
*I observed that if I saw that there were new posts on a thread, clicked on that thread and then clicked back, I would briefly see the new posts notification. The page would then flicker, the page update and the notifications would be gone.
Not that this addresses the Ship-side contribution to the problem, but one way to address that annoyance generally - be it the Ship, craigslist, or pornhub - is to open the links in new tabs. That way, when you're done with what you did at the link, the original tab is in the same scrolled-to state that you left it.
That works on iOS. I don't have a Mac, So I cannot test it there.
Not that this addresses the Ship-side contribution to the problem, but one way to address that annoyance generally - be it the Ship, craigslist, or pornhub - is to open the links in new tabs. That way, when you're done with what you did at the link, the original tab is in the same scrolled-to state that you left it.
That works on iOS. I don't have a Mac, So I cannot test it there.
It's generally an option of most browsers, on most operating systems.
tinyurl (and similar) is very useful for the (very rare on this software*) occasions when the URL contains a character that isn't recognised - I can't remember what I linked to recently where the URL coding wouldn't work for that reason. Generally, retaining the original link is useful because it's easier to see what the link will take you to before you click on it. It seems quite a lot of faff to copy a link, go to somewhere like tinyurl to get a shorter link, then come here and post it into the url code block with replacement descriptive text. But, that's possibly just me not wanting to muck around more than necessary.
* one of the reasons we had for upgrading from the UBB platform was that quite a few commonly accessed websites used characters in URLs that the boards software thought shouldn't be there (Wikipedia was a particular site where this happened a lot) and thus these links wouldn't work.
Coding a URL can be a bit of a faff on an iPhone as the [ ] are two taps away from the main keyboard. I’ve made life a bit easier for myself by creating two keyboard shortcuts: +u for [url=, and -u for [/url]
Not that this addresses the Ship-side contribution to the problem, but one way to address that annoyance generally - be it the Ship, craigslist, or pornhub - is to open the links in new tabs. That way, when you're done with what you did at the link, the original tab is in the same scrolled-to state that you left it.
That works on iOS. I don't have a Mac, So I cannot test it there.
It's generally an option of most browsers, on most operating systems.
Works differently, though. If you open a new tab in Firefox on win7, preview doesn’t work. It does in safari on iOS.
And I never noticed the jump on Firefox, win7
tinyurl (and similar) is very useful for the (very rare on this software*) occasions when the URL contains a character that isn't recognised - I can't remember what I linked to recently where the URL coding wouldn't work for that reason. Generally, retaining the original link is useful because it's easier to see what the link will take you to before you click on it. It seems quite a lot of faff to copy a link, go to somewhere like tinyurl to get a shorter link, then come here and post it into the url code block with replacement descriptive text. But, that's possibly just me not wanting to muck around more than necessary.
* one of the reasons we had for upgrading from the UBB platform was that quite a few commonly accessed websites used characters in URLs that the boards software thought shouldn't be there (Wikipedia was a particular site where this happened a lot) and thus these links wouldn't work.
It’s much quicker on a tablet or phone to open a new tab and create a quick tiny url than using BBcode and trying to get the title of the link in the right place - a right faff without a mouse.
A further note on firefox, win 7. Clicking on a thread and then hitting the back button does give one the refreshed page with the updated new post indicator, but maintains one's previous position. No Jump.
So something changed in the way Safari interacts with the ship software.
If that was to me, then we have a missed communication. Firefox,win7 displays the new page. But it also remembers page position. iOS and whatever version of MacOS Brojames is using, jump back to the cached page then refreshe the page but fail to retain page position.
If that was to me, then we have a missed communication. Firefox,win7 displays the new page. But it also remembers page position. iOS and whatever version of MacOS Brojames is using, jump back to the cached page then refreshe the page but fail to retain page position.
macOS Catalina 10.15.4, and iOS 13.4.1 both have this behaviour.
I don't use the automatic link system, just type in the code, which translates OK to phones and tablets. And the semicolon is equally two clicks away on an Android keyboard and features in lots of BBCode.
If that was to me, then we have a missed communication. Firefox,win7 displays the new page. But it also remembers page position. iOS and whatever version of MacOS Brojames is using, jump back to the cached page then refreshe the page but fail to retain page position.
macOS Catalina 10.15.4, and iOS 13.4.1 both have this behaviour.
I have iOS 13.4, didn't bother with the .1 update. ISTM, this seems to be something in the way Safari handles refreshing a page. Chrome on iOS has the delayed refresh, but manages to remember prior page position. Firefox on iOS behaves like Firefox on win7 in that it displays the refreshed page without a delay when going back and maintains page position.
Further indicating that this is a Safari issue.
If that was to me, then we have a missed communication. Firefox,win7 displays the new page. But it also remembers page position. iOS and whatever version of MacOS Brojames is using, jump back to the cached page then refreshe the page but fail to retain page position.
That actually depends on how you have set up the browser. My Firefox browsers on 5 computers all instantly destroy all cookies and cached info from all websites when a browser tab is closed. Yes, this is via some extensions, and tinkering in about:config (enter that in your http location bar) but it does signify that it is browser dependent.
Apple updates all sorts of things automatically. I suspect iOS users have had an update. Windows10 also does some auto updating. Though I avoid both Apple and Microsoft like the plague, I am exposed to both operating systems daily.
So something changed in the way Safari interacts with the ship software.
Safari has always gone to the top of the previous page when hitting the back button for me. I thought it was just how the software worked.
Hmmm. Could be, I'm not usually reading threads on the bottom of the page, so I mightn't have noticed.
What is new is the hesitation and then refresh. I hit the back button, see the same number of new posts as before I clicked on the thread and then, after a hesitation of about 2 seconds, the page refreshes.
The hesitation may well be simply due to an overall reduction in internet speed now that everyone is having to use it for meetings and stuff.
Not getting it on my laptop using the same connection.
I noticed the issue on my mobile directly after updating to iOS 13.4. It doesn’t happen on my mobile on chrome.
All those things are variable and could be coincidental. But I’m not convinced they are
Not trying to start a rumour but recently o n two separate computers a weird fault occurred. There was an error screen and the PCs went dead for a while but later recovered. On both occasions I was posting on the ship. If I'm the only one good.
IIRC, the Ship software runs on a very spartan amount of code. It's unlikely that other web pages (FB, I'm looking at you) load correctly while SoF doesn't, but you might want to check if you've any OS updates pending.
Comments
display of startpage.com
Then, if I click OK, the address appears in my message but the box doesn't go away. I may be wrong, but I seem to remember that clicking OK used to dismiss the box.
If I repeatedly click OK, the address appears multiple times.
If I click Cancel, nothing happens.
The only way to dismiss the box is to click somewhere within the message itself.
I call that "broken."
The Cancel button does not work -- that is correct.
The box immediately below the one called 'categories' is called 'recent discussions'...that is the one I am having issues with on my android using Chrome. There is pages and pages of white space to scroll past before I get to the 'recent discussions' link. ....but I suppose it could be the same issue if the categories box is massive. Been happening several days now.
I've had this a few times and it makes no difference which entry point I use (i.e., I'm signed out, sign back in again, click on anything that might lead to a discussion, and am kicked out a second or third time).
I’m noticing a changed behaviour on my iPhone. It is irritating and now mimics behaviour I was already seeing in Safari on my laptop.
If I access a thread from ‘Recent discussions’, and then use the back button to go back to the ‘Recent discussions’ page, it initially returns to the place on the page where I left it, but then jumps to the top of the page. It doesn’t matter so much if it is one of the top few threads, but it is pretty irritating if I have been down near the foot of the page and have to scroll all the way down again to find where I was.
It began happening after the most recent upgrade to the iOS that I did, 13.4. SO there is something new in Safari that interacts with the ship software differently than before.
*I observed that if I saw that there were new posts on a thread, clicked on that thread and then clicked back, I would briefly see the new posts notification. The page would then flicker, the page update and the notifications would be gone.
It's generally an option of most browsers, on most operating systems.
(Link example, takes you to a wiki page about dogs, what else? 🐕)
https://tinyurl.com/yaagn79l
* one of the reasons we had for upgrading from the UBB platform was that quite a few commonly accessed websites used characters in URLs that the boards software thought shouldn't be there (Wikipedia was a particular site where this happened a lot) and thus these links wouldn't work.
And I never noticed the jump on Firefox, win7
It’s much quicker on a tablet or phone to open a new tab and create a quick tiny url than using BBcode and trying to get the title of the link in the right place - a right faff without a mouse.
So something changed in the way Safari interacts with the ship software.
Further indicating that this is a Safari issue.
Safari has always gone to the top of the previous page when hitting the back button for me. I thought it was just how the software worked.
That actually depends on how you have set up the browser. My Firefox browsers on 5 computers all instantly destroy all cookies and cached info from all websites when a browser tab is closed. Yes, this is via some extensions, and tinkering in about:config (enter that in your http location bar) but it does signify that it is browser dependent.
Apple updates all sorts of things automatically. I suspect iOS users have had an update. Windows10 also does some auto updating. Though I avoid both Apple and Microsoft like the plague, I am exposed to both operating systems daily.
What is new is the hesitation and then refresh. I hit the back button, see the same number of new posts as before I clicked on the thread and then, after a hesitation of about 2 seconds, the page refreshes.
I noticed the issue on my mobile directly after updating to iOS 13.4. It doesn’t happen on my mobile on chrome.
All those things are variable and could be coincidental. But I’m not convinced they are
Just sayin'