9 nov 2013 03.08 Karl DeSaulniers:
> body nav li#about-us {
> /*Apply styles for current page*/
> }
>
> Does the same thing.
No, it doesn't. :-)
You need one varying page (or rather site section) identifier that is different
on every page as in the as you will have several descendent select
On Nov 8, 2013, at 5:12 PM, MiB wrote:
>
> 8 nov 2013 23.47 John D:
>
>> What is the advantage of using an ID here?
>
>
> Identifying a particular page on the site. This can be used for instance in
> descending selectors for the navigation:
>
> body#about-us-page nav li#about-us {
> /*Apply
8 nov 2013 23.47 John D:
> What is the advantage of using an ID here?
Identifying a particular page on the site. This can be used for instance in
descending selectors for the navigation:
body#about-us-page nav li#about-us {
/*Apply styles for current page*/
}
//and with class for a select
> Since
> there is (by definition) exactly one element, and since it
> is highly unlikely that any other element should be styled
> identically to the element (in all aspects, that is,
> not just in some aspects such as the choice of font-family),
> then I would have thought that an ID was to
8 nov 2013 12.08 Karl DeSaulniers:
> I just Id the container div and go from there.
Well, I guess the more we are moving away from the page concept as such towards
marked up self-containing and context-adapting "packages" that could turn up in
several places, then any page construct identified
On Nov 8, 2013, at 4:30 AM, MiB wrote:
>
> 8 nov 2013 03.09 Karl DeSaulniers:
>
>>
>> Ah I see. Well normally you wouldn't put an ID on the body anyways, you
>> would put a class wouldn't you? That is if your trying to style it.
>
> What's the logic behind choosing a class attribute here? Is
8 nov 2013 03.09 Karl DeSaulniers:
>
> Ah I see. Well normally you wouldn't put an ID on the body anyways, you would
> put a class wouldn't you? That is if your trying to style it.
What's the logic behind choosing a class attribute here? Is it mostly for
semantic reasons? Semantically I can s
> On Nov 8, 2013, at 1:56 AM, Philip TAYLOR wrote:
>
>
>
> Karl DeSaulniers wrote:
>
>> Ah I see. Well normally you wouldn't put an ID on the body anyways, you
>> would put a class wouldn't you? That is if your trying to style it.
>
> Personally I would not (recommend a class in preference
Karl DeSaulniers wrote:
> Ah I see. Well normally you wouldn't put an ID on the body anyways, you would
> put a class wouldn't you? That is if your trying to style it.
Personally I would not (recommend a class in preference to an ID
in order to apply styling to the element, that is).
The nor
Le 8 nov. 2013 à 11:09, Karl DeSaulniers a écrit :
> Well normally you wouldn't put an ID on the body anyways, you would put a
> class wouldn't you? That is if your trying to style it.
Dunno, there are arguments to made in favour of an ID (e.g uniqueness) and
against it: quite high specifici
On Nov 7, 2013, at 7:55 PM, Philippe Wittenbergh wrote:
>
> Le 8 nov. 2013 à 10:47, Karl DeSaulniers a écrit :
>
>> Istn't the rule that inline styles trump all even browser added styles or
>> users styles as they may be?
>> If your wanting it to stay one color, then wouldn't > style="backgro
Le 8 nov. 2013 à 10:47, Karl DeSaulniers a écrit :
> Istn't the rule that inline styles trump all even browser added styles or
> users styles as they may be?
> If your wanting it to stay one color, then wouldn't style="background-color: green !important;"> do the job?
Yes sure inline styles o
On Nov 7, 2013, at 7:40 PM, Philippe Wittenbergh wrote:
>
> Le 7 nov. 2013 à 19:36, Rick Lecoat a écrit :
>
>> Tangential question: One thing that I noticed from the info that the
>> web-inspector provided about the iPhone page was that the body tag's id
>> attribute gets set to 'screen-view
Le 7 nov. 2013 à 19:36, Rick Lecoat a écrit :
> Tangential question: One thing that I noticed from the info that the
> web-inspector provided about the iPhone page was that the body tag's id
> attribute gets set to 'screen-view'. Each of my pages has an id on the body
> tag based upon its url
On 6 Nov 2013, at 23:13, Philippe Wittenbergh wrote:
> Fwiw, as you have a Mac, you can connect your iOS device via USB to your Mac,
> load your page in Mobile Safari, then open desktop Safari (6 or newer),
> Developer tools > iPad simulator (or iPhone …) and inspect the page, just as
> you wo
That was it, Chris, thanks. In fact I'd seen that in my earlier googling, but
I'd discounted it because I knew I hadn't added any webkit overflow rules in my
css. But your post prompted me to take a closer look and I found that I had
that exact rule -- but I hadn't added it myself, it was a bit
Le 7 nov. 2013 à 04:40, Rick Lecoat a écrit :
> Ack, sorry, yes. Copy-pasted from the wrong tab.
> http://www.azathoth.lecoat.com/news
I don’t see the issue on an iOS 7 device.
I’d suspect your use of ‘-webkit-overflow-scrolling: touch;’, given all that
little dance toggling the overflow prop
Ack, sorry, yes. Copy-pasted from the wrong tab.
http://www.azathoth.lecoat.com/news
Thx
--
Rick Lecoat
On 6 Nov 2013, at 19:29, Chris Rockwell wrote:
> I think that link is for your local machine.
__
css-discuss [css-d@lists.
Maybe will help: (via
http://benfrain.com/z-index-stacking-contexts-experimental-css-and-ios-safari/
)
*So, what’s the take away here? Simple. If you are having problems with
z-index’ing items and you have the position property applied and a correct
z-index value applied, ensure you don’t have a C
I think that link is for your local machine.
On Wed, Nov 6, 2013 at 2:11 PM, Rick Lecoat wrote:
> I've got a drop-down menu on one of my navigation items, which is
> position:absolute, with a z-index of 300 (I tend to set z-index in large
> increments). When hover-actiavted it appears over some
I've got a drop-down menu on one of my navigation items, which is
position:absolute, with a z-index of 300 (I tend to set z-index in large
increments). When hover-actiavted it appears over some text; that text has
position:relative and z-index:0. It all works fine, including in IE8+, /except/
i
Thanks, that did work. I didn't get the last css-discuss mailing that
had those replies.
--
Debbie
On 11/5/2010 4:22 PM, Alan Gresley wrote:
Thierry Koblentz wrote:
Oops - I spoke too soon.
I fixed the Flash-overlapping-the-menu issue, but I have one last
problem in IE7 only. The image scrol
Thierry Koblentz wrote:
Oops - I spoke too soon.
I fixed the Flash-overlapping-the-menu issue, but I have one last
problem in IE7 only. The image scroller (#mainscroll) is also
overlapping the menu. I tried a z-index but not working, it's this
page:
http://www.redkitecreative.com/projects/perf
>
> Oops - I spoke too soon.
>
> I fixed the Flash-overlapping-the-menu issue, but I have one last
> problem in IE7 only. The image scroller (#mainscroll) is also
> overlapping the menu. I tried a z-index but not working, it's this
> page:
>
> > http://www.redkitecreative.com/projects/performanc
Oops - I spoke too soon.
I fixed the Flash-overlapping-the-menu issue, but I have one last
problem in IE7 only. The image scroller (#mainscroll) is also
overlapping the menu. I tried a z-index but not working, it's this page:
http://www.redkitecreative.com/projects/performance/
--
Debbie
w
That fixes it, thanks very much!
--
Debbie
On 11/5/2010 11:45 AM, Alan Gresley wrote:
Debbie Campbell wrote:
On this site:
http://www.redkitecreative.com/projects/performance/contact-us/
if you hover on Browse Our Inventory, in IE7 the hovered menu is
hidden behind the #maincontent div.
I
> > http://www.redkitecreative.com/projects/performance/contact-us/
>
> if you hover on Browse Our Inventory, in IE7 the hovered menu is hidden
> behind the #maincontent div.
>
> I tried this:
>
> >
>
> But no. Can someone please help?
This is because in IE "position:relative alone creates a
On 11/5/2010 1:10 PM, Debbie Campbell wrote:
On this site:
http://www.redkitecreative.com/projects/performance/contact-us/
if you hover on Browse Our Inventory, in IE7 the hovered menu is hidden
behind the #maincontent div.
I tried this:
But no. Can someone please help?
IE7 and under
Debbie Campbell wrote:
On this site:
http://www.redkitecreative.com/projects/performance/contact-us/
if you hover on Browse Our Inventory, in IE7 the hovered menu is hidden
behind the #maincontent div.
I tried this:
But no. Can someone please help?
Your screen CSS has this.
#mainc
On 11/5/10 1:10 PM, Debbie Campbell wrote:
On this site:
http://www.redkitecreative.com/projects/performance/contact-us/
if you hover on Browse Our Inventory, in IE7 the hovered menu is
hidden behind the #maincontent div.
I tried this:
But no. Can someone please help?
Try:
Best,
On this site:
http://www.redkitecreative.com/projects/performance/contact-us/
if you hover on Browse Our Inventory, in IE7 the hovered menu is hidden
behind the #maincontent div.
I tried this:
But no. Can someone please help?
--
Debbie
www.redkitecreative.com
_
christi...@netscape.net wrote:
> On this site I have a hover effect on the photos on the right. Works good in
> Firefox and IE8 but on IE7 the larger version of the image appears behind
> everything else. I have tried tweaking z-index values of several elements but
> to no avail so far. I'll kee
Question: Are the images at the bottom of the page supposed to be cut off?
On Tue, Sep 29, 2009 at 2:33 PM, wrote:
> On this site I have a hover effect on the photos on the right. Works good
> in Firefox and IE8 but on IE7 the larger version of the image appears behind
> everything else. I have
It's probably not a good idea to have a photo pop up that is so
pixelated.
IE support for :hover is buggy, from what I read when I Googled it.
You might want to correct your CSS - there are 7 errors.
Theresa
On Sep 29, 2009, at 12:52 PM, christi...@netscape.net wrote:
>
>
> You need to gi
You need to give us the link to the site...?
?
Theresa
Yes, I am also absentminded. Here it is:
http://www.flowerscostamesa.com
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/lis
You need to give us the link to the site...
Theresa
On Sep 29, 2009, at 12:33 PM, christi...@netscape.net wrote:
> On this site I have a hover effect on the photos on the right. Works
> good in Firefox and IE8 but on IE7 the larger version of the image
> appears behind everything else. I ha
On this site I have a hover effect on the photos on the right. Works good in
Firefox and IE8 but on IE7 the larger version of the image appears behind
everything else. I have tried tweaking z-index values of several elements but
to no avail so far. I'll keep working on it but if someone sees a s
Hi,
I am working on a layout which involves element overlapping and i'm
concerned that I am not setting the stack order correctly.
The reason I need to set stack order is that I have overlapping interface
elements which must display above of the other content.
example:
/* CSS */
#step_two_
xtiandc wrote:
> My only thought was to enforce the z-index not on the parent (scrollbox), but
> rather on its children (hover), hence really only come into play when visible
> and thereby leaving the text link not "covered" by scrollbox. I dunno if it's
> even possible.
>
Sure, but on the o
Ingo Chao <[EMAIL PROTECTED]> wrote: Ingo Chao wrote:
> The testlink can only be placed over or under this stacking context of
> scrollbox, further or nearer to the user.
And the dilemma is, that in your concept, scrollbox must have this width
and height to bring overflow:hidden into play. Scr
Ingo Chao wrote:
> The testlink can only be placed over or under this stacking context of
> scrollbox, further or nearer to the user.
And the dilemma is, that in your concept, scrollbox must have this width
and height to bring overflow:hidden into play. Scrollbox has to clip the
menu.
I don't
xtiandc wrote:
> I put together a simpler version of the page for feedback:
> http://demo.wfp.com/flyout.htm
>
> As is now, no z-index's are specified. The menu is placed at the
> bottom of document and therefore inherits the higher value (I
> assume). This means that the link to the left does no
I put together a simpler version of the page for feedback:
http://demo.wfp.com/flyout.htm
As is now, no z-index's are specified. The menu is placed at the bottom of
document and therefore inherits the higher value (I assume). This means that
the link to the left does not work (strangely enough,
43 matches
Mail list logo
