I have been very aggrevated lately when I notice ALL my hyperlinks are underlined in Firefox; however, when I edit in Frontpage 2003 they are not underlined and there are no underline tags. Is there a flaw in firefox in reading the html or is their something wrong with Frontpage? I have also had big issues with Firefox not reading Embedded .wmv files.
Frontpage (a Microsoft product) will occassionally do things in a Microsoft only way. They've gotten much better with this in recent versions, however. We could try to help you fix it if you attach a copy of the page or post a link to the site.
whenever html/htm or web presentations did in products like MS word and frontpage , they add unwanted tags... my personal experience is that the pages created with WORD will only appeared in IE,becz all code is in VML.so by removing those messy code , you can get a better look.
A big YES, I've had the problem so many times with underlined and not-underlined link. My solution that works for both is as follow: Code generated by Frontpage (this looks fine on IE but NOT on FireFox): I manually change this code to: The modified code will produce link that is not underlined in BOTH IE and FireFox. Hope this helps!
YES! You are the first ever to solve this problem for me (I've asked at about 15 forums and still no solution). A HUGE THANKS!
My pleasure NRLMedia. It's only because I've encountered it millions of times, so I thought I'd share it. It'll be fussy to change the manual codes though, but since FireFox users are rising, to me, it's worth the effort to cater for FF users.
A better solution - don't use Frontpage! Seriously though. I've encountered numerous issues with sites done in Frontpage and then viewed in Firefox, or any non-MS browsers. That's why I won't ever use Frontpage.
I tried using Dreamweaver but it's so different compared to Frontpage I'm just not willing to switch. CSS does work well.
Yes, agreed. I was lost with Dreamweaver. Both programs are generating HTML anyway, so the difference would be minuscule. Save it here and there. And one could go on about the pros and cons. Plus, I have found too many tricks with Frontpage that helped me reduced my work (for example: mass find-and-replace of HTML codes for 40-50 HTML files at one go!).
Actually, in my experience, it is rare that FrontPage produces HTML. It produces markup, and within that markup it'll throw in some HTML. But a considerable amount of what it creates is also not (X)HTML, and so the difference is much greater. To be fair, I have not messed with the latest release. Dreamweaver is ok too. Sometimes it gets lucky and writes decent code. www.nvu.com is the best WYSINWOPG (What You See is Not What Other People Get) editor, as far as I'm concerned - the price is definitely right! I'm strictly a handcoder, but when someone asks what I recommend for WYSINWOPG, I generally recommend nVu.
To take things one step farther, often times Frontpage has issues when writing html and viewing in IE
I'm willing to bet it does because it doesn't use css exclusively. Using css along with xHTML 1.0 code is the best way to be consistant between the various browsers out there.
i used css ,eventhough i found difference firefox and IE in colors.some colors don't suit with FF but will look perfect for IE. you can see the differnence live here "http:// sefdb.info/tools/" i wonder why colors looks alike in some browsers eventhough every color is generated from RGB Hexadecimals.