I have a simple SPA that uses HTML 5 Notifications in Chrome and Firefox, works great. For IE , Pinned sites looks like the best supported options (without a plugin) that I can use. I've seen some literature here and on in the docs about using xml config and metadata for setting this up, just curious if there is a way to have a Pinned Sites notification (icon in task bar) show up when , say, an ajax call finishes that loads new content into the page. I guess a good metaphor would be a chat application that uses ajax to load messages, when a new message comes in, I want to put an icon in the task bar .
Found this library that does all the lifting for you regarding pinned sites :
https://github.com/bsatrom/pinify/blob/master/js/jquery.pinify.js
No metadata needed.
Related
I am fiddling with Blazor WebAssembly to make a PoC and try to convince some people to start using it to develop Intranet web apps. However, our standard browser for Intranet content is IE11. Since Blazor WebAssembly is not supported in IE11, it may as well be the best thing in the world but I believe we will not get off to a good start by saying "This does not run in IE11, so people must use Edge for this particular app".
In order to minimize this issue, I was wondering how to make some URLs open on Edge. I know this is possible because if I paste a Teams meeting URL onto IE11, the page is not rendered and a new Edge window opens up automatically instead. Does anyone have any idea how to accomplish this?
From your description, it seems that you want to open an Edge window from IE 11 browser and view the website, right?
In this scenario, I think you could try to use the URL Scheme: microsoft-edge:{website url}. Then, it could open the Edge browser from IE 11 browser.
Sample code as below:
link
[Note] If you are viewing the website on IOS , the URL scheme should like this: microsoft-edge-http:// or microsoft-edge-https://.
I've been trying to create mechanism for my Expo app, that will allow users to share content of app (so I basically need linking with params, and I think I know how to do it, according to docs).
I wanted to start creating this mechanism with simple sharing, without params (just clickable link that opens app). Here's my code (executed when user presses share button):
share = async () => {
await Share.share({
message: Linking.makeUrl()
})
}
It shares link as excepted (I tried it on messenger), but shared link is not clickable. I also tried using exp://192.168.100.3:190000 that points to my PC in the same LAN (I coped that from http://localhost:19002/), where metro bundler is running, and copying Tunnel link - neither of those worked, link is just a plain text, and if user clicks on it nothing happens. But, when I scan QR code, from http://localhost:19002/ (metro bundler page) application opens as excepted.
You're doing everything just fine!
The reason why a shared link is not clickable in some apps is simply because of the mechanisms of the other apps for "detecting" links from plain text and "linkifying" them.
You see, these links are actually "deep links" (custom URL schemes).
Here's an example. If I share this link: exp://192.168.100.3:190000 over Slack, it becomes "clickable", because it looks like Slack has a mechanism to detect these custom "deep links" which lead to a mobile app:
If I share the same link over Messanger, it outputs it as a plain text. This is because Messanger doesn't have a mechanism to detect these "deep links".
In order for the link to "click", it must be rendered in an anchor tag. Messenger simply linkifies only "known" web links (http://, https://...), not custom ones.
The QR code reader in your case opens your deep link, because it has a mechanism to detect "deep links".
So, if you want a reliable way for making your links always "clickable", here's the workaround: spin-off a web site. When people generate (and share) links, they share web links https://your-server. When they open these links -> the web server redirects them with the exp://... (or your custom) scheme. If users have your app installed - the links will open with your app.
I've deployed a React Redux site on hostgator.com. While it works to visit the page and navigate as usual. (React routing works), it shows 404 not found whenever I reload the page.
I talked to their support which, before leaving 20 sec into the conversation, came with the suggestion that it may have to do with the site trying to run on https, while no SSL is implemented.
I'm curious, why does it work locally and not on the world wide web? Any thoughts?
Thanks.
You need to look into a Server Side Rendering solution. A good framework for doing so with React is Next.js.
Basically as long as you don't refresh the page React-Router has control over the address bar as well as history via the History API. But when you hit refresh you send a request to the server for whatever is in the address bar. But the server is not handling your routing, React-Router is on the client side. You also won't be able to type a child route directly into the address bar without server side rendering.
Previously in the OSX WebView, we had the WebResourceLoadDelegate callbacks to get informed about the events related to the resources embedded in the page we are loading. I used these calls to filter and redirect the HTTP requests coming from the page itself. Now, this functionality seems to be completely missing in WKWebView (OSX 10.10 beta 3), and I didn't find traces of it in the public WebKit source either.
Does anybody know how am I supposed to work this around?
ps. for the record, I've already submitted a feature request at rdar://17695683 .
When writing a Worklight app it is verboten to change the URL of the DOM in which the application is running. This makes sense as a hypertext move to another URL will obliterate the state of the app.
On occasion however, in my app I receive a URL for a news article and the user wishes to read it. Displaying the new content in an iFrame would start to address the requirement, but then I need navigation controls, etc. and it starts to feel like I am reinventing a wheel.
Does Worklight, or one of the mobile JS frameworks provide a "browser in browser" experience that I need here?
Worklight utilizes Cordova. Cordova makes it possible to display just what you wanted, a "browser in a browser" - InAppBrowser.
The InAppBrowser is a web browser view that displays when calling
window.open(), or when opening a link formed as <a target="_blank">.
Try that.
No setup is required as the InAppBrowser plug-in is already part of the Worklight project (this may differ depending on your Worklight version; If you are using 6.x you're OK).
All you need to do is to call up the URL. For example, in yourProject\apps\yourApp\common\main.js:
function wlCommonInit() {
window.open('http://apache.org', '_blank', 'location=yes');
}
Once the app initializes it will open the InAppBrowser:
And once tapping the Done button, you're back in the app.
You can of course not specify the location attribute so the navigation bar won't display. In that case, in order to go back to the app the user will need to tap the Back button: