Before posting this I passed one full day to understand this bug but without any result.
Here is the link to web application that Im developing : https://yd-chauffeurs.vercel.app/
This BUG is happening ONLY in SAFARI. Please use SAFARI to reproduce. In other browser it works perfectly.
Open Home page and click on CONTACT after the contact page is opened click on ABOUT (A PROPOS in french) or GALLERY. You will see that SAFARI doesn't scroll to that section which is marked with id.
When you are on Home page and you click , all Links work perfectly and they scroll to necessary id.
But when you are on another page like Contact or FAQ, Safari doesn't scroll to About or Gallery.
I can't figure out why.
Thank you for your answer.
Today I finally managed to resolve the issue. I resolved this problem by giving min-height to service section.
The problem was that Safari was not charging all DOM elements so it was starting to scroll to the section but when DOM was fully loaded the scroll was pushed upper. So I gave min height to service section and now it works perfectly.
Thank you again.
I checked in Safari Version 14.1 (Desktop) but cannot reproduce the problem.
We have an app that works fine in Edge and Chrome, but Firefox will not display the HTML generated by AngularJS. The app is using ui-router and components. Inspecting the page using the Developer Tools, you can clearly see the HTML, but it is greyed out and not visible on the page. What's going on?
I have a simple react app, to get to this app, a user clicks an anchor tag from another page. This is . Let's say this page is http://localhost/index.html
It redirects fine to the react app. Let's say it's on http://localhost/react/simple_app. In this react app, I use React Router, which has a catch all if none of the route matches. It will simply render text "Page Not Found".
When I click back button to get to index.html, both Chrome and Firefox will reload simple_app, WITH the url set to http://localhost/index.html. Obviously this will make simple_app to render "Page Not Found", as the route http://localhost/index.html is not defined in its routes. Once that rendered, the browser will immediately renders the previous page. So on this action the user will see the correctly rendered previous page. Everything seems to be pretty minor so far, just a bit of a flicker when "Page Not Found" briefly rendered then it quickly re renders index.html.
What is not fine is, if I then press "Forward" page on the browser, it will NOT re-render simple_app again. It will simply shows "Page Not Found". My suspicion on this is because briefly it has rendered it prior to moving "backwards" (with the wrong URL), hence browser will load it from cache.
Tried on firefox and chrome, with reactjs. Although this behaviour can be replicated with any JS, but specifically problematic with react router.
Also tried, if I type in the url http://localhost/simple_app, if i click back, it won't do the funky reloading with the wrong URL.
Not sure if any good solution to prevent this from happening.
To help everyone who got here looking for an answer, after a bit of digging and a bit of luck, I found the issue rooted in a library (ruby gem) we used called turbolinks. https://github.com/turbolinks/turbolinks.
This gem, injects javascripts which intercepts various navigation API such as anchor tag and browser back and forward so that it can make as our native application behaves like a Single Page App (without reloads).
So if you encountered similar behaviour, you may not be using Ruby, but check if you are using library that behaves similar to Ruby's Turbolinks. Hope this helps.
In Chrome, default page scroll sometimes show and sometimes not during the page navigation in the angularjs. Chrome version is "Version 52.0.2743.116 m".
I Googled on it and found that one of the old version of Chrome had this issue and in later version it was resolved.
Any helps will be appreciated!
Thanks in advance.
In some browsers (ex ie7) where angular is not working I want to display a message telling the user to have his browser updated or use another one.
The way I am doing this is
<div ng-if="false">Browser not supported</div>
If the angular cannot render then the ng-if will not be processed so the div is displayed.
This is also causing a flicker when testing for pages with protractor because the protractor is going from page to page very fast.
My question is: Does anyone have a better solution of treating this kind of situation?