Is this the right place to report this issue:
A similar thing is happening at the top of /page/1 etc. This is on a 1st Gen iPad (iOS 5) in Safari.
Hmm, iOS5 and iPad 1 are quite old.
If I had the means I would upgrade, at least so I wouldnât have to deal with⌠the astonishment of support staff who canât cope with the idea of anyone using equipment older than a somewhat arbitrary date.
Youâve no idea how annoying that is, especially when I would like nothing better than a new(er) iPad, not to mention a desktop machine. Some of us have no choice in the matter, not if we want to continue to eat.
I donât know what is so difficult about making sure that the site furniture will fit on an old iPad screen, but it fit before the latest site upgrade, so whatâs changed?
1 Like
Couple new issues:
The site wonât conform to my browserâs width (~ 1150 px), adding a horizontal scroll bar. There doesnât appear to be any extra-wide content that requires it, either.
The BBS view has hijacked my browserâs in-page search function. When I press ctrl-F itâs supposed to bring up Firefoxâs own search utility, but now it forces me to use BoingBoingâs.
Iâve experienced the control/â-F issue for certainly longer than a few months, on Chrome mostly. The workaround I use is control-G to âfind againâ, which hasnât yet been hijacked.
2 Likes
This only happens on topics with more than 20 posts. Not all posts are loaded in the browser, only the visible part of the stream, so the native browser find function wonât work as you expect.
That said you can press find key twice to override as needed.
1 Like
I got a weird one this evening. Between when a new post goes up on BB and the automatic post gets created here on BBS, the link on the bottom of the BB postâs javascript apparently canât handle the null and reverts back to the old CSS.
HTTPS is now enabled on both BB and BBS. So the âhttps anywhere is interfering with stuffâ problem should appear nevermore.
2 Likes
/ wince
Ordinarily this work wouldnât be undertaken in a production environment.
1 Like
Your deep knowledge and expertise are appreciated and helpful.
ummm doesnât ir eventually have to be done to production? unless you have the resources to swap out dev/prod regularly? and it is probably less pain to just update/upgrade production after testing is doneâŚ
Well obviously you need to issue the changes to production, but yes, after testing. I.e. You donât tweak things on a live site and hope for the best.
Any time.
This topic was automatically closed after 765 days. New replies are no longer allowed.
