jQuery Forum

I assume you have css like…

.page-nav{display:none}

http://jsfiddle.net/jakecigar/a94j9aj5/ <--

Also, just to clarify, I only need to click twice after page loads, after clicking twice initially then one click works.

I loaded my css into js fiddle. 

No, there is no .page-nav {display:none}

Im actually clicking an icon inserted using the :before pseudo class.

In any case, here's the css:

Here's the new fiddle:

I need to figure out how to load font awesome icons in jsfiddle so the icon Im clicking will display

I would add //maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css
as an "external resource". But that didn’t help much.

http://jsfiddle.net/jakecigar/a94j9aj5/5/ <--

You need to load the font itself, as well as the CSS. And the CSS assumes that the font is located in a directory relative to the the CSS:

So, it will try to load the font from a location relative to the origin, not relative to where the CSS was loaded from. On Plunkr, you can put the fonts in the right place, or you can modify the CSS.

(Well, on jsFiddle, I guess you could drop the whole mess into the CSS editing window...)

I use FontAwesome, though I'm considering switching to SVG icons - seems to be the consensus now. I myself have experienced the fiddling you have to do with positioning in order to get font icons to go where you want them to go.

But... do you need FontAwesome to demonstrate your problem? It seems a distraction when you say you have a problem with an anchor element.

It's always best to chop-down demos to the minimum needed to show the problem. In fact, you will often discover what the problem was as you do that!

I dont think I need font awesome to identify the problem. Should be able to substitute any small icon. 

Just havent had the time to identify and insert the needed code into jsfiddle to reproduce the problem.

Or a simple text link.

You need to set-up port-forwarding, to forward from port 80 on you router's Internet interface, to port 80 (or whatever port you use for http) on your development machine.

Note: some Internet providers will block port 80, because they might not permit you to run a website on your home Internet connection. You have to pick some different port, then. Port 8080 is popular! In that case, you do not have to change the port number on your development computer - just on the Internet side, in order to work-around the port block.

You have to check with the legalities. But, if you read the find print, it is usually fine when you are using it for development/test. They just don't want you running a permanent website and bring hordes to your Internet connection. And/or nobody is going to notice this level of activity.

Secondly, it is convenient to sign-up with some dynamic domain service. You can get these for free or cheap. Your IP address will probably change periodically, unlike a professional web hosting set-up where you get a permanent IP. You will install some little plugin or application, that will keep the service up-to-date with your current IP address. Or, many/most current routers support many of the popular services directly, and so you just plug in your service user ID/password right on your router setup.

You might also get your own domain name, and then you can use it with the dynamic IP service. Otherwise, you can use a subdomain on the dynamic service.

P.S. Since it's such a common reason for using a dynamic IP service, the service will almost certainly have instructions on how to do the port-forwarding for common routers! And they will surely tell you how to set-up the update with common routers.