Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > HTML > gap rendered in Firefox 3 but not in IE 7

Reply
Thread Tools

gap rendered in Firefox 3 but not in IE 7

 
 
dorayme
Guest
Posts: n/a
 
      06-15-2008
In article <Xns9ABE1747DD61neredbojiasnano@85.214.90.236>,
Neredbojias <me@http://www.neredbojias.net/_eml/fliam.php> wrote:

> On 14 Jun 2008, dorayme <> wrote:
>
> >> > > Your CSS rule removes all the margins on all
> >> > > elements, even those which have no relation with the noticed gap.
> >> >
> >> > That does not mean it is useless as a quick check on something, to
> >> > give a clue on how to investigate further.
> >>
> >> Then use a targeted, specific check on the margin-top of the targeted
> >> element. You do not need to over-use, abuse, over-kill.

> >
> > "Overuse, abuse, overkill" for zeroing margins and/or padding with a
> > universal selector for a quick check? These strong words sound more
> > appropriate when the target is something more substantial than a
> > temporary diagnostic tool of elimination.
> >
> > In many cases one does not quite know what element to target. It is
> > hardly abusing anything if it is used to eliminate something from the
> > enquiring diagnostic mind.
> >
> > I understand your view about the dangers of zeroing margins and
> > paddings by use of the universal selector. But this is not at all
> > relevant. No amount of describing the evils of such universal zeroing
> > intended for permanency will be obviously relevant to its use as a
> > temporary measure of diagnosis.
> >

....
>
> If one has no idea what the problem is, a
> universal change will hardly really help,


If a 2 sec zeroing of the margins makes the unwanted phenomena
disappear, you know it might well be a margin problem and you can look
more locally then. So your contribution makes no reasoned sense to me.

--
dorayme
 
Reply With Quote
 
 
 
 
dorayme
Guest
Posts: n/a
 
      06-15-2008
In article <Xns9ABE26D046BA9neredbojiasnano@85.214.90.236>,
Neredbojias <me@http://www.neredbojias.net/_eml/fliam.php> wrote:

> On 15 Jun 2008, dorayme <> wrote:
>
> >> > I understand your view about the dangers of zeroing margins and
> >> > paddings by use of the universal selector. But this is not at all
> >> > relevant. No amount of describing the evils of such universal zeroing
> >> > intended for permanency will be obviously relevant to its use as a
> >> > temporary measure of diagnosis.
> >> >

> > ...
> >>
> >> If one has no idea what the problem is, a
> >> universal change will hardly really help,

> >
> > If a 2 sec zeroing of the margins makes the unwanted phenomena
> > disappear, you know it might well be a margin problem and you can look
> > more locally then. So your contribution makes no reasoned sense to me.

>
> Not really. If one element has unwanted/inadvertant/mistaken padding and
> the adjacent element has a wanted default margin, you've just "identified"
> the wrong problem thru carelessness.


What has this got to do with using say * {margin: 0} for less than 2
seconds (in which time you do *not* try to identify anything positively
or "fix" anything or run into any dangers whatsoever. You just look to
see if some unwanted look is affected for the better. If you think it is
a waste of time, make sure you never do it, not even to waste 2 sec.
Others will use it and it will often be worth the 2 secs.

To see this point, you need to understand the spirit in which it is used
and not jump to too many conclusions.

--
dorayme
 
Reply With Quote
 
 
 
 
dorayme
Guest
Posts: n/a
 
      06-15-2008
In article <Xns9ABE98CB48F77neredbojiasnano@85.214.90.236>,
Neredbojias <me@http://www.neredbojias.net/_eml/fliam.php> wrote:

> On 15 Jun 2008, dorayme <> wrote:
>
> >> > If a 2 sec zeroing of the margins makes the unwanted phenomena
> >> > disappear, you know it might well be a margin problem and you can
> >> > look more locally then. So your contribution makes no reasoned
> >> > sense to me.
> >>
> >> Not really. If one element has unwanted/inadvertant/mistaken padding
> >> and the adjacent element has a wanted default margin, you've just
> >> "identified" the wrong problem thru carelessness.

> >
> > What has this got to do with using say * {margin: 0} for less than 2
> > seconds (in which time you do *not* try to identify anything
> > positively or "fix" anything or run into any dangers whatsoever. You
> > just look to see if some unwanted look is affected for the better.

>
> Well, I never have used it, and even though it's only 2 seconds, 2 seconds
> wasted here and 2 seconds wasted there...


You are right not to use a technique that you do not understand in the
slightest way.

--
dorayme
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Our gap: Tech jobs coming, but the labor pool is lacking. bilawal samoon Python 0 09-26-2009 05:57 PM
firefox problem, html not rendered correctly Jeff ASP .Net 1 04-20-2009 02:07 AM
backgroundcolor not rendered with Netscape, Firefox André ASP .Net 4 06-19-2008 07:30 PM
<br> not interpretered but just rendered. Louis. Javascript 5 07-22-2006 08:15 AM
Gap in IE, no gap in FF chlori HTML 1 01-19-2006 09:30 PM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57