I am following a tutorial for developing a simple Facebook app, yet the sample code will not work in Firefox (works fine in IE) - it literlly just displays the code, all on one line.
Full code is here, if it is helpful - http://pastebin.com/YggfCQEH
Can anybody tell me why this is not working? I've no doubt that this is something really simple, but I cannot spot what is wrong. Thanks.
Most likely your server returns mime/type text/plain. What is the filename? Chances are, if it's not .html or .htm that is the problem.
The issue here was that the encoding was UTF-8, and apparently Firefox does not like that. Changing the encoding to ANSI sorted the problem.
Maybe you can try to find some other working page on that server, and check what is the files extension that generates correctly, and rename your file with the same extension as that.
Firefox has an option in the View menu you may check. View>Page Style, if No Style is selected FF will disable all CSS and leave you with just html, that's my first guess. (I only suggest this since you say its only FF and this solved a friend's problem just the other day...)
Your code looks fine, but there could be something in the js file screwing it up... i'd double check functions.js for anything weird.
Related
I am very, very new, so please pardon my ignorance.
I was away (thus using PC's) and have learnt to use embedded css and had my practice website going ok, then I came home to face my Mac.
(I have not learnt to use a separate CSS, because that was hard to do on borrowed computers so I only know embedded and in-line CSS)
No matter what I do (the file was already formatted to be plain text, saved as html), I cannot get any CSS property "linked" to my html. The html codes are showing, but the CSS seems completely lost. I took a screen shot of the very simple example. The right part is the what shows on the browser. Can you please enlighten me?
Did you try other browsers?
There are some similar issues in this page css not working in safari.
After you try other browsers with the newest version, you can locate the problem. If other browsers also don't work, the problem might arise from your code.
I'm having a weird issue where I'm sure I've written the CSS fine, however the browser isn't picking up the classes.
When checking the file on my hosting provider I see that the classes seem to be registered wrongly. I'm thinking the issue might be here.
classes shown with different ui colouring to others
Anyone know what the issue might be?
When checking the file on my hosting provider I see that the classes seem to be registered wrongly. I'm thinking the issue might be here.
Codes are fine. Your host probably render the colours of the code wrongly.
But i don't see you use the .hero-home anywhere on http://www.jardox.com/. Probably the reason why you didn't see any change?
Edit: There's some problem with the characters. change them to utf-8?
I have a problem that has me stumped and I'm hoping someone here can help me solve it. I designed a new site using Sublime and am having problems with one file(page) that looks great on Sublime, but is screwed up when I put it on the live server.
From Sublime it renders perfectly on all web browsers, so I don't think has anything to do with it. I suspect that maybe it has something to do with the Cascading part of CSS. But, I don't know how to determine that.
Anyhow, here's the the code involved: http://portabledogpotty.com/dog-potties.html
The first section is the HTML and the second section is the CSS file. Any help would be very greatly appreciated!
Sam
Seems you have a table only for the header **SAVE EXTRA MONEY WITH OUR VALUE PACKS! **, try to put it as a th in the table for packs.
I see that just using the chrome element inspector.
Grettings
I see sfdocready in some footers of pages I have been working on. I cannot find anything about this?
For example:
<sfdocready id="sfDocReady"></sfdocready>
Thanks!
This has to do with Superfish (the <sfdocready> and <sfmsg> tags).
I just determined what was doing it in my case. Using Safari, I have (well, had, it's gone now for this bizarre behavior) the Awesome Screenshot extension installed. There is a checkbox in its settings called "Enable similar product search powered by Superfish" which looks for images on the page and uses them as search parameters to provide comparison shopping deals for you.
In its defense it did prompt me if I wanted to see price comparisons, but it did so on Amazon in a way that actually looked like the prompt came from Amazon.
To the answer above me about Firefox inserting it when you save the document, that's only because an extension or some JavaScript inserted it first, it has nothing specific to do with Firefox. It also has nothing to do with Wordpress.
Somewhat sleazy stuff, imo.
This looks like it's got something to do with Wordpress themes.
I have, an assumption, that this tag means: "safe document is ready", so something is running only after whole document has been loaded. But what exectly does it mean and how does it work, it`s a big question.
Near this tag I have also also often seen <sfmsg> tag.
This tag is inserted by Firefox when you save the page as an HTML document.
I issued this problem yesterday. I have firefox with a plugin named Awesome Screenshot. In order to solve this you need:
Click over the Awesome Screenshot
Select options
UNCHECK/DISABLE the option: "Enable similar product search powered by Superfish"
And that is all!
An interesting issue which I've googled and can find absolutely no reference too, perhaps because I'm too vague on the cause myself.
I have a simple jsp page that is run from a struts 2 action. It' fairly javascript heavy, but its an internal app on my company's intranet so thats not a great problem.
All seems normal so far, right? but interestingly, the last few tags on this page fail to render. This is true for all browsers I've tried it in (IE, FF, Chrome).
What I mean by not rendering is that they simply don't exist when you view the source! whats worse, in IE, half a tag declaration is actually printed as text at the bottom of the page. All very odd.
But what makes it even stranger, if I put a few <br /> tags after the </html> tag, then all browsers render down past the </html> tag, but still cut off the last few <br />'s.
Has anyone ever heard of anything like this? I don't even know where to start troubleshooting! I know my description is vague but that's only because I'm a bit vague on it myself.
If 'View Source' does not show you the tags then it is not a rendering problem, but a server or network problem, as the content is not being delivered to the browser.
It sounds like a buffer flush problem to me. Have you got any filters that might be buffering the html before it gets to the browser?
Sounds like you have an unclosed quotation mark somewhere. Or something like that. Stuff like that can mess up even the source view as some browsers don't show the exact bytestream they received in the socket in source view (I know for a fact that IE used to do this). Try doing a GET with wget or a telnet client or something similar and see what happens.
We should see the code of your jsp to answer. I suspect there is an unclosed tag or a an unclosed quotation mark of an attribute - as DrJokepu said - in the jsp.
That is the first time I have heard that IE is behaving the same way as the other browsers; by accident...
But seriously, is the html error-free?
I recommend using the html validator extension for Firefox to show you if the html is producing any errors or warnings.
There has to be an error somewhere, but without the code it is impossible to say what it is.
I had a problem some time back with a web-site that was getting 'cut-off' and similarly, I solved the problem with a quick hack but never a proper solution. What it came down to for me was that the web server seemed to require the content-length of the page for it to render properly. When I buffered the output and added the content length, the page would load in full. Different technology though - this was an application built on Perl CGI running on Apache 2.2.
Thanks for the assistance all, but unfortunately none of these seemed to help. I've found a hacky way around it and since its not a critical app, It'll just have to do.
thanks again