fullpage.js navigate back by url hash not work in mobile - fullpage.js

<body>
<div data-anchor="page_1"></div>
<div data-anchor="page_2"></div>
<div data-anchor="page_3"></div>
<div data-anchor="page_4"></div>
</body>
When I open my home page http://my.site/index, the default page is
page_1 and there is no hash part #page_1 in URL.
I slid down the screen and current page changes to page_2 with URL
http://my.site/index#page_2
I navigate back and the URL changes to
http://my.site/index. The page is still on page_2 which I wanted
is page_1.
Are there some options on creating fullpage.js or should I set the default URL to http://my.site/index#page_1?

Unfortunately that's a well known bug in fullPage.js for which there's no solution so far.
You can read more about it on the repo's github issues forum:
https://github.com/alvarotrigo/fullPage.js/issues/950
To prevent this, you can force fullpage.js to ignore the anchors by using the options recordHistory: false or lockAnchors: true.

Related

Firefox requesting content inside HTML5 template before activation

I was debugging my web app using DevTools when I noticed that Firefox is requesting url defined in src attribute of an img that is located inside a HTML5 template tag, while Chrome doesn't.
I'm using the last version (50.0).
Is this a bug?
Example below:
<template id="object-img">
<div class='object-container'>
<div>
<img src="cacaca.jpg" class="img-responsive" alt="imagem" />
</div>
</div>
</template>
It's a kind of optimization from Firefox.
The image is requested only the first time if it is not already in the browser's history / cache. Subsequent reload of the page won't trigger the request again.
The problem is that the image inside the <template> is requested before the following but normal images in the rendered DOM, which could be counterproductive in some situations. A solution is to put the <template> after the other images.
Note: the template specifications state that the elements in the template are not rendered, but they are parsed. They say nothing about preloading of referenced resources.

Generate Pinterest Share Button That Specifies URL

I am trying to create a "pinterest share" button, but am running into a snag.
Currently, I have the pinterest button (generated from their Widget Builder) appearing in a Lightbox. (For certain reasons, it must appear this way.)
The issue is the Lightbox code has direct linking on it, so the code for the lightbox window is something like: www.domain.com/#/social/4
Pinterest is picking up that URL (which has no images since it's just the lightbox) instead of the URL for the main page (www.domain.com).
Does anyone know how I can specify the exact URL to share via the pinterest button?
I have read some posts that said doing this would work:
<img src="//assets.pinterest.com/images/PinExt.png" alt="Pin it" / > <script type="text/javascript" src="http://assets.pinterest.com/js/pinit.js"></script>
However, specifying the URL does not seem to work at all. It appears to be totally ignored and has no impact.
Any ideas?
Thanks in advance!
You can use a standard link and specify all the data in the parameters:
<a href="http://www.pinterest.com/pin/create/button/
?url=http%3A%2F%2Fwww.flickr.com%2Fphotos%2Fkentbrew%2F6851755809%2F
&media=http%3A%2F%2Ffarm8.staticflickr.com%2F7027%2F6851755809_df5b2051c9_z.jpg
&description=Next%20stop%3A%20Pinterest"
data-pin-do="buttonPin"
data-pin-config="above">
<img src="//assets.pinterest.com/images/pidgets/pin_it_button.png" />
</a>
Source: http://developers.pinterest.com/pin_it/
You can try using structured meta data and Rich Pins.

gog.com's login link missing only in Firefox (for HTTP)

gog.com has a HTTP site (http://www.gog.com/) and a HTTPS site (https://secure.gog.com/).
When I visit the HTTPS site in Firefox, the Login/Sign-up link is visible:
When I visit the HTTP site in Firefox, the link is missing:
But when I visit the HTTP site in Chromium, the link is visible:
So gog.com doesn't seem to hide the login link in general on HTTP. In fact, if I disable the CSS, I can see the login form on the HTTP variant on Firefox, too:
I contacted the gog.com support, but they were not able to reproduce it.
I tested it with three different Firefox installations on different systems, and I never saw the Login/Sign-up via HTTP. Is it only me?!
I checked the source code with Firebug. For HTTP, the relevant part seems to be:
<div class="nav_user">
<div class="nav_empty not_logged"></div>
</div>
For HTTPS, it looks like:
<div class="nav_user">
<div class="nav_link nav_account nav_login" data-hoverclass="hover_acc">
<span class="nav_login_icon"></span>
<span class="nav_text">Login / Sign-up</span>
<div class="nav_hover"></div>
</div>
<div class="nav_cart_h">
<div class="nav_empty"></div>
</div>
</div>
Does someone have an explanation for this? Why does it work in other browsers but not in Firefox?
EDIT: Other things on their HTTP site don't seem to work in Firefox either (but on HTTPS without any problems). For example I can't use the big carousel on the home page: clicking the navigation arrows doesn't do anything, clicking at one game neither.
So all these problems are probably related to JavaScript? Does Firefox have any security features that disallow some functions on HTTPS or something like that?
For whatever reason, gog.com requires local storage for HTTP (but not HTTPS).
So the about:config setting dom.storage.enabled needs to be true.
(Similar problem with JS on anime.stackexchange.com and japanese.stackexchange.com)

iframe and Remarketing Code Madness

So I have nearly finished working on an a eCommerce platform with Magento and we are now running Remarketing campaigns via Google's Ad Display Network.
Now...
If you look here: http://img211.imageshack.us/img211/8859/52447256.jpg
I had placed the remarketing tag underneath my footer links and it has caused those links to be shifted on the bottom and in the center where as before it was flush and tidy on the right hand side in line with the newsletter opt-in form.
What's causing this is the iframe width. If I set '300' to '0' then its back to how it should be and perfectly in line.
Now the problem...
I placed this remarketing tag in magento and the code does not provide any iframe html code. I checked the footer by going to:
\MY WEBSITE\html\app\design\frontend\base\default\template\page\html\footer.phtml
What did I find? Barely anything lol. So now I am confused as to where this iframe was created and how to solve it. Any ideas would highly be appreciated!
Steve.
I ran into same problem just yesterday while working in a shitty Comarch Aurum CMS and was looking for a safe solution which wouldn't get me banned:
Google remarketing tag - iframe height issue
so if anyone else has this problem, the most common solution is to insert the conversion.js script tag into a hidden div:
<div style="display: none">
<script type="text/javascript" src="//www.googleadservices.com/pagead/conversion.js"> </script>
</div>
src:
keanrichmond.com/google-remarketing-messing-with-my-design.html

AJAX Wordpress Site with Difficult URL settings

On this WordPress theme utilizing AJAX, proves to be difficult. The developer of the theme cannot seem to find the issue or solution to it.
This site runs beautifully, if, and only IF, you type is this complete URL "http://www.geigerandwood.com/#!//" if you type in the .com site alone, it will appear but will be disfunctional.
I have made attempts in 301 redirects, even creating a static page with a redirect but still no luck. Is there something that I can add or change in the code to make this work properly?
FYI - it has been tested on the common web browsers on both OSX & Windows.
Here is a video of my presented issue. http://www.screenr.com/D1G8
What theme do you use?
My quick examination of your page source code is that I only can find something related to the #!// is in here
<div id="contentBoxScroll">
<a id="closeButton" href="#!//"></a>
<div class="dragcontainer">
<div id="contentBoxScrollDragger" class="dragger">
<div class="scroll_up"></div>
<div class="scroll_down"></div>
</div>
</div>
</div>
I assume it must be something inside the script from which that HTML is generated. I can say more since I can't see the full source.

Resources