I'm trying to setup Notification api in Opera Browser. My code works in Firefox, Safari, and Chrome. It does not entirely work in Opera GX.
When the notification is created, the banner is only shown after the tab has been changed. It doesn't matter how long ago the notification was created, nor does switching to another application trigger the event. Only selecting a new tab.
Is this expected behavior?
Can I fix it with js?
Can I fix it within Opera GX?
EDIT: peculiar details. It does not trigger the notification when switching to another tab on localhost. Also, the one I'm triggering from is https://localhost:1234 (not an iframe, is https)
Related
1.Clear IE 11 Browsing history, cookies etc.
2.Close the browser
3.Open the browser
4.Navigate to https://www.parcelforce.com
Expected: The parcelforce.com home page should load properly and quickly in IE11
Actual:
Page does not load properly. Also, on refresh the page takes a lot of time to load. Sometimes it may not load.
This issue is happening with IE11 only. Whenever I hit https://www.parcelforce.com in other browsers say chrome, Firefox, safari, website is loading quickly.
Can anyone suggest me what might be the issue with IE11. Should I need to add any code for IE11 to load website quickly?
Based on your description, I reproduced the problem you described. And I found some other things, when using the address bar and enter key (two or more times) navigation can make the page complete loading. But using ctrl+R or F5 to refresh cannot achieve the same effect. I checked the console in ie11 and did not find any error messages (except warning messages), so I am not sure if it is a compatibility-related issue or other issues in the code.
On the other hand, the Internet Explorer 11 desktop application will be retired and go out of support on June 15, 2022, I recommand that you could use some morden browsers, such as Chromium Edge.
For more about retirement FAQ of Internet Explorer 11, please refer to this blog.
I'm trying to add Google Signin to our login page. I've followed the code supplied by Google, as well as a GitHub project that I used for code example. Both work perfect on Chrome, FireFox, Safari, but I can't get it to work on IE11 or Edge.
The GitHub project is at https://github.com/googleplus/gplus-quickstart-javascript. This project uses Google's newer apis.google.com, however I've also tried plus.google.com as suggested in another post. Neither work.
I added a data-onfailure function to the button, and get an error "popup_blocked_by_browser" even though the popup blocker is turned off in the browser. Even though I get this popup error, I do get a popup that asks which Google account to use, but when I choose one, I get the "The webpage your are viewing is trying to close the window" message. If I choose Yes, the window closes, but I don't get logged in.
Anyone have any advice for getting this to work in IE or Edge?
I ran into this problem on IE 11 with Windows 10.
I fixed it and then it happened again after receiving Windows Updates - annoying!
Here is what fixed it for me; it was an IE Setting.
Go to:
IE -> Internet Options -> Security
Check "Apply" and then "OK" To exit.
IE Settings Screen Shot
Finally, restart IE.
When using chrome dev tools to emulate mobile devices, sometimes when toggling emulation from mobile back to desktop the user agent spoofing gets stuck in mobile. I've tried hard cache reset, closing browser completely, restore to default.... but anything I do the site still renders in mobile (even when emulation is turned off).
This happens in Canary, beta, and regular Chrome.
Also a note i've only seen this happen in Sharepoint.
Anyone know how to resolve? Nothing seems to get the dev tools to change user agent back to default when exiting emulation.
Have you tried deleting your chrome settings?
Windows: C:/Users/%username%/AppData/Local/Google/Chrome/User Data
Mac OSX: ~/Library/Application Support/Google/Chrome/
Ubuntu: ~/.config/chromium/
Also make sure you aren't ZOOMED! Gets ya everytime
I ran into this same problem previously when using dev tools in Chrome to look at mobile resolutions that got me permanently stuck in mobile for SharePoint only. I solved it originally with the recommendation above of deleting my Chrome settings folder, however, that meant I had to sign in again, sync my extensions, etc.
After forgetting that this would happen again, I ran into the same issue, but this time I discovered that if you append the following to your SharePoint URL it will reset this back to non-mobile. I verified that it is not temporary as I have closed my browser, reopened, visited SharePoint, and it still loads in desktop mode.
/?mobile=0
So, you would use your site url, e.g. https://siteurl/?mobile=0
Weird, this just started happening to me. It persists in new tabs and new windows. Only fix is to open DevTools and switch to Responsive mode and then pull it way out. As soon as I turn off Responsive / Mobile view, Chrome snaps right back to a mobile view by default (appears to be iPad size).
The solution for me (so far) was to quit Chrome and open it back up.
When I visit the Spotify Play Button demo page (https://developer.spotify.com/technologies/spotify-play-button/) in Opera 11.62, clicking on the Play Button gives me the (mostly-expected) popup:
The application "Spotify" must be launched to open the link:
spotify:
Do you want to proceed?
If I click yes, the Spotify app then launches (if not already running) and gets focus, but does not play anything. I suspect the link is getting broken by Opera somehow (notice that it has the spotify: protocol name but nothing after that). The Play Button on my own site produces the same behavior. Works fine in Firefox on the same machine.
Has anyone else experienced this?
Yes, sadly, that's the case. There's a similar issue in Opera's bug tracker.
I think your particular issue could be related to Opera's lack of support for cross-origin resource sharing (CORS). CORS support is coming is available in Opera Next, but not Opera 11.62. If it doesn't work in Next, I encourage you to file a bug report.
Well, it seems Safari 5.1 at least on Lion which is what I'm using now decides to unload tabs from memory as it deems it necessary.
The big issue with this is sites that display ajax alerts or ones that have chats as for example GMail. I was having 2 conversations on Google Talk right in the GMail website and while I was on another tab I noticed the title blinking indicating new messages in my conversations, as soon as I clicked the tab Safari decided to completely reload the page, losing all those conversations (I don't keep logs of those).
It goes without saying that this behavior breaks modern web apps and seems unnecessary on a desktop computer. I understand the necessity of this on iOS devices due to ram constrains though.
Is there any way to disable this "feature", I couldn't find a way to do so. It's that or switching to Chrome or Firefox, but I like Safari.
Thanks.
I think I have a temporary work around. Pages on my site — petersonguides.com — periodically reload the tab in Safari 5.1. Ordinarily this wouldn't be a big issue, but I have a video that plays in a FancyZoom box and it can't get all the way through without the tab being refreshed.
I tested with Chrome and it doesn't cause the same tab reload behavior, so I'm sure it's a Safari 5.1 problem.
I have JavaScript and PHP on the home page and I thought there might be a conflict, so I started pulling things off and retesting with the video. The last thing I checked was removing the Google Analytics script. That fixed the problem.
I tried bumping up the Database Storage amount - per the previous answer - but that didn't have any effect.
I am having trouble with Pandora (Flash) not advancing songs in a background tab. As a quick-and-dirty test, I went to Preferences > Advanced > Database storage and popped it up from 5MB to 500MB. Flash is still very unstable, but now songs are advancing in the background. I don't know if this will work for you but you might give it a try.
Safari 5.1 | OS X 10.6.8
The reloading of tabs in the background is a feature of Safari 5.1 on Lion. There is currently no easy way to get around this. The only way possible at the moment involves disabling the multi-process window feature:
Enable Safari's Debug menu by typing in Terminal.app, restarting Safari afterwards:
defaults write com.apple.Safari IncludeInternalDebugMenu 1
From the new Debug menu in Safari, select Use Multi-process Windows to remove the tick before it and deactivate this feature.
While this prevents tab reloading in the background it will disable extensions and gestures in Safari. But it can be easily activated again via the Debug menu.