safari – Missing plug-in error when placing the dashboard web clip widget on the desktop

Hello, before I upgraded my MacOS to 10.13.6, I was able to use the following command:

write com.apple.dashboard devmode YES

to Drag my Safari web clip widgets from the dashboard to my desktopbut after updating the operating system version, the error is displayed after placing a widget on the desktop. The widget itself is not displayed and this is displayed error right in the middle of the empty widget which had been placed on the desktop:

Missing plug-in

Despite the dashboard, widgets such as clock and calendar can be perfectly displayed on the desktop.

I googled on it, but found nothing and can not guess what's going on. Also, I can not update my operating system right now. Therefore, I would appreciate some hints for fixing this issue without updating my operating system.
Safari version: 13.0.3 (my operating system version has no updates available in AppStore.

What I tried that did not help:

write com.apple.dashboard devmode NO
write com.apple.dashboard devmode YES
killall Dock
reboot

One of the web clips in the Dashboard is very important to me, so I want to see it back on my desktop.

Thanks for your help!

CSS – Website Scroll does not work on SAFARI

I have a website here missnationglobal.com. Scrolling works fine in Chrome and other browsers, with the exception of Safari.

I've reviewed the CSS markup for the site and am apparently unable to pinpoint the cause. Here is a code:

html {
  height: 100% !important;
  width:100%;
  overflow-x: hidden !important;

  overflow:scroll;
  -webkit-overflow-scrolling: touch; 
  -webkit-overflow-y: auto; /* added css prefix for safari */

}
body {
  height: auto;
  min-height: 100%;
  overflow: hidden;
  position: relative;
  margin:0;
  }

Every help is appreciated!

Terminal – Safari SSH Tunneling Troubleshooting Diagnosis

What diagnosis / troubleshooting can be done to achieve the goal?

Goal: Tunnel through a remote router, with port 22 enabled for SSH access via SSH.

Background:

  1. SSH tunnel construction from the terminal: ssh -D 3000 -N user@mydomain.fqdn.com
  2. Proxy Setup:

Note: Username / pw is accepted by the router on the WAN side.

Enter image description here

  1. Tunnel error displayed: Safari does not return web pages if the proxy is enabled.

  2. Terminal indicates:

    Channel 2: Open failed: administratively prohibited:
    Channel 3: Open failed: administratively prohibited:
    Channel 4: Open failed: administratively prohibited:
    Channel 5: Open failed: administratively prohibited:

The litmus test states that www.whatismyip.com should return the WAN IP address of the FQDN.

What tests can be performed to determine corrective actions? Any diagnostic questions to advance the effort are welcome: Thank you.

safari – How can a public WLAN load the "Accept Terms of Use" page for you to use?

For some time, I've found that my MacBook Air does not load public Wi-Fi sites. All bars in the Wi-Fi icon above are solid, but the page I can connect to will not load. Never really bothered me.

This week, my wife started chemo and radiation therapy. There is a lot to learn when that happens. I had my laptop in the clinic with me to organize some things and check some while she underwent radiation. But I could not connect to their WiFi. I've tried many ideas from my iPhone search, but nothing worked. No frustration I needed.

So today, before I went to the clinic, I searched online again for someone who had a similar problem, and I found this page.

On March 28, 2018, when someone with the same problem as me wrote JBIS wrote this: "Go http://captive.apple.com This is the only way to ensure that it is displayed. " tilt Connect to the Internet and enter it http://captive.apple.com in the search bar.

When they took my wife to the clinic for treatment today, I did just that, and it worked. Your Wi-Fi page was loading and I was able to do the things I needed to do while waiting for my wife. One of the things on my list, later, when she was resting, was to find a way to thank this side and the person who gave this endearing advice.

This site recommends that you need 50 points before you can comment – in my case, "Thanks, JBis" for a helpful response almost two years ago that has done its job today. Therefore, I could not comment on the original post.

We hope that this contribution will allow others to benefit from the solution and recognize the person – JBis – who shared it.

Close the Safari tab and return to the previous app in iOS in a single action?

TL; DR

Is there an action with a tap or a gesture that closes the current Safari tab and returns to the previous app?

motivation

If you click on a website link in many apps, it will open in Safari.

After returning to the site, this tab, which was actually meant for a quick glance at a website, will remain open indefinitely, even if I return to the app by clicking the "Back to app" button in the status bar.

While iOS13 introduced the option "Automatically delete tabs after the time", this does not solve the problem: It likes to remove tabs that I intentionally left open without removing the unwanted tabs immediately,

This is in stark contrast to Android, where pressing the back button on such a tab closes the tab and returns to the app in an interaction. Instead, if you return to the app using the app switcher, the tab remains. This allows a workflow where tabs are discarded by default at a glance. Keeping these tabs is also easy. So I'm looking for a way to reproduce this behavior on my iPad.

While much of the difference could be resolved through app design, the default behavior has a significant impact on the actual user experience.

Example: Kindle app

Kindle eBooks or magazines may contain links to websites. If you click on a link on Android, you can quickly take a look at it. If this was not worthwhile, you can quickly forget this by pressing the back button. On iOS, the tab is kept in Safari, which discourages the click in the first place.

Example: Feedly RSS Reader

For Feedly, it is often preferable for better formatting or, because of RSS feeds containing abstracts only, to open the link to the full article page. On Android, this is currently being delegated to a Chrome tab, using the back button behavior. IOS opens a Safari view, which is somewhat limited compared to the actual opening in Safari. For example, you can not manually correct the URL for bad RSS feeds or use bookmarks. While the software can be configured to open web pages directly in the Safari app, manually closing the tabs is unattractive.

The difference becomes important when the article's reading is interrupted and the Feedly app is closed in the background. If the tab in the browser remains open for later reading on Android, the Safari View on iOS is lost together with the status of the app and the article is marked as read, it will be difficult to find again.

mobile – How to prevent a Scroll Bar from hiding under iOS Safari with Momentum scrolling?

If you add -webkit-overflow-scrolling: touch; For a scrollable element, such as a div, you get a smoother scrolling experience (native momentum scrolling), but lose the ability to keep the scroll bar on. For some reason, Apple has decided that in UX it's good to hide the scroll bar most of the time.

The problem is that if only 3 items are displayed in your scrollable content and the rest is not partially cut, you will not get any indication that a scroll bar exists and other items are available.

I'd like to know if there's a way to have a scrollable div with momentum scrolling, but that never hides.

tokbox – OpenTok says that Safari 13 supports ScreenSharing

The tokbox code for verifying screen sharing support is

OT.checkScreenSharingCapability(function (response) {
    console.log('checkScreenSharingCapability response = ', response);

    if (!response.supported || response.extensionRegistered === false) {

        // This browser does not support screen sharing
        console.log('screen share not supported');
    }
});

The edition in Safari 13 is

checkScreenSharingCapability response =  
extensionInstalled: undefined
extensionRegistered: undefined
extensionRequired: undefined
supported: true
supportedSources: {screen: true, application: false, window: true, browser: false}

Therefore, it states that it is supported and does not work (the documentation states that it is not supported). This is the same answer that Chrome (supported) returns, so the answer itself seems to be wrong opentok / client 2.16.3