-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent the angular-seo script from running when the client is not a bot #11
Comments
You know, I was thinking, maybe we can check for That would need testing though. |
What kind of testing framework would you like to use?. Regards, On Wed, Oct 30, 2013 at 6:01 PM, Steeve Morin notifications@github.comwrote:
|
Oh! I didn't mean a testing framework, I meant testing it does actually work :) In the mean time, can you try a version without any events, only checking for Something like replacing
to
And check if it actually works. |
And of course remove all the event listening code from the server. |
ok, I'll give it a try right now On Wed, Oct 30, 2013 at 6:13 PM, Steeve Morin notifications@github.comwrote:
|
I removed the 'onInitialized', an left the 'onCallback' event untouched. On Wed, Oct 30, 2013 at 6:20 PM, Oleg Belausov hellgy@gmail.com wrote:
|
Seem to work just fine, should I push it in a separate branch and open a On Wed, Oct 30, 2013 at 6:26 PM, Oleg Belausov hellgy@gmail.com wrote:
|
Yeah open a PR, I'll probably merge that once I get to review it. Thank you for your time. |
when i hit url: that time page is not render. how can resolve this issue. my .htacesss file RewriteRule ^(.)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] Tried for SSR -VerishalOptions +FollowSymLinks Production envirment url: |
Some non-modern browsers have an issue with the createEvent and dispatchEvent functions.
For instance IE8 throws a whole bunch of errors.
To fix this I suggest to implent a feature that prevents the script from running when the client is not a bot.
currently I am using the following setup to fix this:
angular-seo-mock.js:
The text was updated successfully, but these errors were encountered: