Using Safari on macOS to view this forum
-
Hi all, I just got my first printer with a duet and joined the forum to help learn the ropes. I tend to use safari on macOS which is working just fine for DWC. However, when I view this forum from my desktop mac, I get the mobile version of the site. I get the desktop version when I use Chrome.
I searched the forum to see if there was some setting I could change, but no joy. Sorry if I'm missing something obvious. I can just continue to use Chrome, but if there is a way to change the Safari behavior, I'd appreciate knowing about it.
Joe
-
@bitsplusatoms Here is a guide how to view mobile websites in desktop Safari - just do it the other way round by either choosing the first („Default“) or second ("Safari") menu entry.
-
@infiniteloop Thank you. I should have mentioned that I already tried changing the user-agent via the develop menu to no avail. Does that work for you?
-
@bitsplusatoms I'm on Mac but don't use Safari. However I have just tried the forums in Safari and had no issues, the desktop version loads fine.
It's a responsive website so the layout changes depending on your actual screen size. If you are seeing the mobile version it is likely 1 of 2 things, your browser window is too small or you are zoomed in.
To reset the zoom level to default
View > Actual Size, or Command 0
BTW Command + or Command - for zooming in and out.
-
@bitsplusatoms I can get Safari to show the forum in mobile mode, by narrowing the browser window and/or increasing magnification, on Mac (OS X Mojave). So try widening the browser window and resetting zoom as @richardmckenna suggests.
I have seen reports of getting stuck in mobile mode if you use hand-off from an iPhone. If resetting zoom doesn't work, try deleting Duet3D cookies and cache data (Preferences->Privacy-> "Remove All Website Data"). Safari keeps passwords in another place so if you have saved passwords you won't lose them in the process.
Edit: now points at correct people!
Ian
-
@droftarts it's not my issue, I was replying with a possible fix.
-
@richardmckenna Oops, replied to wrong person, sorry!
Ian
-
@droftarts Thank you. View > Actual Size did the trick.