hey, i am unhappy to see when my design looks perfect in IE i just installed firefox and it looks totally wack, it plays with the tables and makes it look bad...
wot u guys think
suggestions
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 07:01 AM
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 06:41 AM
- ehdwma created topic »Hide "Register new account" and change template to 3 col« 06:27 AM
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 01:29 AM
- mdee created topic »How to implement returnpage ?« 01:00 AM
- nestormateo responded to »Fillters in Clip« 24. May
- damon responded to »Can the Updated Version Check be Turned Off (Z 1.3)« 24. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Firefox stuffs up designs
-
- Rank: Legend
- Registered: Dec 11, 2002
- Last visit: Oct 21, 2009
- Posts: 11674
Actually, it's the other way around. Firefox does things properly, and IE has all the bugs in it ;)
--
itbegins.co.uk - Zikula Consulting
birtwistle.me.uk - Personal Blog
Please read the Support Guide -
**unknown user**
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 1097
FordsRule
wot u guys think
That you should drop IE for general use and use it only to compare your design if it is displayed correctly.
Until IE 7 comes up and IF it does the job correctly, IE is to be banned as an Internet bug ! -
**unknown user**
- Rank: Helper
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 676
Without a link, hard to comment. Microsoft stopped developing IE once they deemed the Browser wars won, which has left a lot of bugs or simply inconsistent browser behavior unfixed. Some of it is quite deliberate, like its box model, not necessarily bad, but sticking to a set standard like the W3C's would help everybody design consistent webpages. But then, they were never in the business of helping anybody but themselves, so proprietary methods, like JScript, is a way to get ppl to stick with IE. AOL has just released the Netscape 8 browser, cobbled together from both IE and Mozilla. It uses IE for 'trusted' sites for what they call "maximum compatibility", and Gecko for the rest. That's an unfortunate side-effect of this kind of thinking. But at least they recognise Gecko as being more secure :)
MS has recently reconstituted its IE group to counter the Firefox threat, originally they were only gonna update it with each Windows update, considering it an extension of Windows itself. A lot of the main bugs have apparently been fixed for the upcoming Beta, since it was already on the cards when they were disbanded a few years ago, so it's largely a matter of implementing it. PNG-24 transparency has at last been implemented. But of course, IE7 will still be backwards compatible to render older pages in IE's old quirky way. Actually, IE6 does have a Standards mode, but it's off by default. The default rendering method is BackCompat mode. The way to turn it on is to provide a full DocType declaration, complete with the DTD address, as in
As for the quirks, you should learn to code to W3C standards, then tweak if necessary to get it working in IE. There's a number of hacks, sadly necessary for advanced CSS, utilising IE's own bugs against it. My favourite is the Star-HTML bug, where a CSS rule starting with * HTML will be interpreted by IE, but no other modern browser, since it selects selects everything before the HTML element, which is nothing. Eg
.classname { width: 180px; }
* HTML .classname { width: 200px; }
will compensate for IE's box model, where you use margins and padding totalling 20px. -
**unknown user**
- Rank: Senior
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 2330
FordsRule
hey, i am unhappy to see when my design looks perfect in IE i just installed firefox and it looks totally wack, it plays with the tables and makes it look bad...
wot u guys think
suggestions
Welcome to the real world! :) If FF displays bad, then likely so will Netscape.
Seriously though...if you use w3c compliant code, you won't have many issues, if any at all. It's a good idea to preview as you go in FF, NS, IE and Opera...the first few times you start designing... you'll quickly get a handle on it. It takes less than an afternoon to discover the quirks between browsers.
You should strip the tons of attributes you've used in your HTML, and place them into the style sheet where they belong as a starting point.
Also, as msandersen noted, you can bypass the quirks mode (of all modern browsers) by using the DOCTYPE declaration. Use it!! It will cause your pages to render more closely in appearance to one another.
Don't use CSS hacks!! Using hacks causes non-standard methods to live on.... -
- Rank: Expert
- Registered: Dec 02, 2002
- Last visit: Apr 30, 2010
- Posts: 1474
Quote
PNG-24 transparency
Best thing since sliced bread...
When I design a layout I have two browsers open; IE6 and Firefox. During the full dev process I constantly check the layout in both browsers. You would be wise to do this also :)
-Lobos
--
-Lobos
Professional PHP Framework Services: Concept, Development and Deployment -
**unknown user**
- Rank: Helper
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 676
That's the only use IE has to me these days :) Even when they get around to "fixing" IE, I wouldn't care to go back, but of course for the majority they just use what comes with their machines, which alas is IE for Windows-weeners. So you can't ignore it.
Unfortunately, for some things, CSS hacks are necessary, short of not using CSS2/3 methods at all. A full DocType can make IE render with W3C standards only so far, there's a number of well-known bugs in IE which can only be gotten around by a hack, like adding an extra 3 pixels for IE to get around a rendering bug, for instance. This is not due to bad design practices by anyone, but inherent IE bugs. -
**unknown user**
- Rank: Senior
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 2330
I'm from the opposite end I guess. Unless told to do otherwise, I only use CSS that translates well across the spectrum (which is still quite a lot to work with). This keeps extra browsers from hogging my taskbar as well. ;) -
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 86
ok, check out the borders difference between firefox + IE
i want it to look like the IE one? how do i fix it?
http://fordsrule.com -
**unknown user**
- Rank: Senior
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 2330
You should really clean up your HTML...you've got styles and attributes everywhere and it makes it a hard read...a style sheet will allow you (and us) to find glitches easily...
In your HTML, I'm seeing stuff like this:
Code
border-left-style: solid; border-left-width: 1" bordercolor="#225690"
...which can be (well, should be) combined (and put in the style sheet):
Code
border-left: 1px solid #225690;
border-right: 3px dotted #xxx;
etc; etc;
If you want it to be x-browser, you're going to have to move your borders into the style sheet I'm pretty sure. And in your CSS, for most every numeric value, you need a "measurement" ... ie, you won't say border:1 ... you'll say border:1px ... or it won't work x-browser...
I _think_ that almost every attribute of your tag is an MS proprietary tag, so you'll want to get rid of those. (including bordercolor...) MS tags will probably only work on IE and Opera.
Since, I'm nit-picking...;)... you've got code like:
Code
TABLE WIDTH=778 BORDER=1 CELLPADDING=0 CELLSPACING=0 height="125"
...you need to unCAPS the tags/attributes... and always quote the attributes...
- Moderated by:
- Support
