Re: [css-d] CSS Via Conditional Comments for Safari?

2011-12-26 Thread david 

David Laakso wrote:

On 12/24/2011 3:20 PM, david wrote:

Philip TAYLOR wrote:


Barney Carroll wrote:


I am incredibly pretentious ;)


You think you really have to tell us that, having already written :

there are no credible user personas who fire up Windows and Mac to 
make sure their experience of a site has bitmap parity


???! :-)


I just thought of one ...


Web designers.

I suspect most everyone else pretty much uses only one browser on one 
platform at a time. Although a growing number use both a desktop PC OS 
and a smartphone.



 That's nice. How dose that help OP? And if the OP is not concerned 
about it, now... just why did she write about it in the first place? In 
my estimation the font in question remains a real-world problem and 
ignoring that issue for a reason that happens to be convenient at the 
moment does not make it go away.


I didn't say anything about ignoring it. Just mentioned it cuz site 
visitors who visit using one of the OS/browser combos that shows the 
font the way the designer likes it won't know that it has problems on 
some other combo.


I'm boring when it comes to fonts. Can I read it comfortably without 
having to zoom it out-out-out-out-out-out? Fine, that's all I need from 
a font.


--
David
gn...@hawaii.rr.com
authenticity, honesty, community
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] CSS Via Conditional Comments for Safari?

2011-12-26 Thread david 

Elli Vizcaino wrote:

That's nice. How dose that help OP? And if the OP is not concerned
about it, now... just why did she write about it in the first
place? In my estimation the font in question remains a real-world
problem and ignoring that issue for a reason that happens to be
convenient at the moment does not make it go away.


Because I thought there was a way to fix make fonts identical via
Safari conditional comments - something I've come to learn is
strictly for IE browsers only. After seeing the screen shot that
Phillipe posted I deemed it wasn't as bad as I thought just on my
windows version of Safari and some other browser Phillipe pointed to
which has low usage. I agree with what Barney had to say and I think
he is 100% right! Sorry David but this is not about ignoring a real
world issue for reasons that happen to be convenient at the moment. I
don't think anyone ever has designed/build a website to render 100%
identical across every single browser in existence. One has to decide
at what point it's good enough and what one can live with, you just
don't happen to agree...


I saw one once. I think someone on this or webdesign-l mentioned it as a
joke. Every single character on the page was done as an in-line image of
their chosen font at their chosen font size (and color). ;-)

--
David
gn...@hawaii.rr.com
authenticity, honesty, community
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] css to suit the cms

2011-12-26 Thread Ram 
I need to replicate an existing website to Alfresco CMS (content management
system). How to deal with existing CSS to work in the CMS.

The aim is to have the CSS  HTML that could be integrated with the templetes 
in CMS. 
The HTML, CSS is pre-existing and CSS need to be tweaked such a way that
the site is replicate/migrated well for the Content management system.
Any tips or pointers in terms of CSS while replicating the site in CMS?

Thanks,
Ram
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] Vertically centreing in Strict HTML 4.01

2011-12-26 Thread Aaron Gray 
Is there another way with HTML 4.01 strict to vertically and horizontally
centre an img within a page other than boxing it by div's and turning
them into 'display: table' and 'display:table-cell', and aligning them to
center, middle ?

Many thanks in advance,

Aaron
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] css to suit the cms

2011-12-26 Thread mem 
On Dec 26, 2011, at 13:11 , Ram wrote:

 Any tips or pointers in terms of CSS while replicating the site in CMS?
 

Hello,

I'm a little fish, and this is a little tip that I'm not even sure if it's a 
good one.
But, if your CMS makes some inline styles, it would be nice to develop your own 
CSS and place !important on those rules that you know your CMS shouldn't 
override;

k. regards,
mem
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] Two validator parse errors - why ?

2011-12-26 Thread mem 
Hello all,

If we validate this CSS as CSS 3 :

http://dev.zoom.org.pt/

You will see that the validator will trow two parse errors.

I don't understand what am I missing here;

The css related file should be:
http://zoom.dev/styles/main.css

Any clue about how can we fix those errors ?


Thanks in advance,
mem

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Two validator parse errors - why ?

2011-12-26 Thread Jukka K. Korpela 

2011-12-26 15:29, mem wrote:


If we validate this CSS as CSS 3 :

http://dev.zoom.org.pt/

You will see that the validator will trow two parse errors.


Both error messages are caused by the same syntax error, namely the use 
of 1. as a line-height value. In CSS, a number that contains a decimal 
point needs to have at least one digit after the point, so you need to 
use just 1 or 1.0 or perhaps some other well-formed value. (Setting 
line-height: 1 usually creates too tight setting.)



The css related file should be:
http://zoom.dev/styles/main.css


That's not the CSS file referenced in the HTML document specified, and 
zoom.dev doesn't even seem to exist.


Yucca
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Two validator parse errors - why ?

2011-12-26 Thread mem 
On Dec 26, 2011, at 13:58 , Jukka K. Korpela wrote:

 2011-12-26 15:29, mem wrote:
 
 If we validate this CSS as CSS 3 :
 
 http://dev.zoom.org.pt/
 
 You will see that the validator will trow two parse errors.
 
 Both error messages are caused by the same syntax error, namely the use of 1. 
 as a line-height value. In CSS, a number that contains a decimal point needs 
 to have at least one digit after the point, so you need to use just 1 or 1.0 
 or perhaps some other well-formed value. (Setting line-height: 1 usually 
 creates too tight setting.)

Thanks a lot for the clarifications.

 
 The css related file should be:
 http://zoom.dev/styles/main.css
 
 That's not the CSS file referenced in the HTML document specified, and 
 zoom.dev doesn't even seem to exist.

Indeed dev.zoom.org.pt since that address is a local one. Sorry. :(

 
 Yucca

Thanks a lot.
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] two drop downs / z-index / conflict

2011-12-26 Thread Bob Meetin 

The demo site: www.dottedi.us/18

I am working on a joomla theme/template.  The mainmenu works fine by itself.  
For the requirements I needed to add a secondary, dropdown menu module.  The 
second menu will live above the main dropdown.  The problem is that in spite of 
adding some high z-index numbers in what I think is the right stylesheet, upon 
hove the upper menu is getting obscured.

This gets a little convoluted because of the module/theme css structure.  I added the 
following to the dropdown.css stylesheet for the artgrandmenu module:

/* Added by Bob  just to see */
.artgrandmenucontainer ul.dropdown li.hover,
.artgrandmenucontainer ul.dropdown li:hover {
z-index: 987654321;
}

#ja-search .artgrandmenucontainer ul.dropdown li.hover,
ul.dropdown li:hover {
z-index: 987654321;
}

#ja-search .artgrandmenucontainer ul.dropdown a.hover,
ul.dropdown li:hover,
#ja-search  a.hover,
#ja-search .artgrandmenucontainer a.hover,
a:hover
{
z-index: 987654321;
}

#ja-search {
z-index: 987654321;
}

I'm stabbing at anything now.  I am not looking into the main menu stylesheet, 
thinking that I should look at the secondary menu. I commented out everyything 
in helper.css

mod_artgrandmenu/mod_artgrandmenu/css/dropdown/themes/default/helper.css
mod_artgrandmenu/mod_artgrandmenu/css/dropdown/dropdown.css
mod_artgrandmenu/mod_artgrandmenu/css/dropdown/themes/default/default.css

Ideas?

--
Bob Meetin

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] two drop downs / z-index / conflict

2011-12-26 Thread Nghia Nguyen 
Try to set z-index of ja-mainnav to -1.

-Original Message-
From: css-d-boun...@lists.css-discuss.org
[mailto:css-d-boun...@lists.css-discuss.org] On Behalf Of Bob Meetin
Sent: Monday, December 26, 2011 1:03 PM
To: CSS-D
Subject: [css-d] two drop downs / z-index / conflict

The demo site: www.dottedi.us/18

I am working on a joomla theme/template.  The mainmenu works fine by itself.
For the requirements I needed to add a secondary, dropdown menu module.  The
second menu will live above the main dropdown.  The problem is that in spite
of adding some high z-index numbers in what I think is the right stylesheet,
upon hove the upper menu is getting obscured.

This gets a little convoluted because of the module/theme css structure.  I
added the following to the dropdown.css stylesheet for the artgrandmenu
module:

/* Added by Bob  just to see */
.artgrandmenucontainer ul.dropdown li.hover, .artgrandmenucontainer
ul.dropdown li:hover {
z-index: 987654321;
}

#ja-search .artgrandmenucontainer ul.dropdown li.hover, ul.dropdown li:hover
{
z-index: 987654321;
}

#ja-search .artgrandmenucontainer ul.dropdown a.hover, ul.dropdown li:hover,
#ja-search  a.hover, #ja-search .artgrandmenucontainer a.hover, a:hover {
z-index: 987654321;
}

#ja-search {
z-index: 987654321;
}

I'm stabbing at anything now.  I am not looking into the main menu
stylesheet, thinking that I should look at the secondary menu. I commented
out everyything in helper.css

mod_artgrandmenu/mod_artgrandmenu/css/dropdown/themes/default/helper.css
mod_artgrandmenu/mod_artgrandmenu/css/dropdown/dropdown.css
mod_artgrandmenu/mod_artgrandmenu/css/dropdown/themes/default/default.css

Ideas?

--
Bob Meetin

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/ List policies --
http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] two drop downs / z-index / conflict

2011-12-26 Thread Bob Meetin 

On 12/26/2011 11:23 AM, Nghia Nguyen wrote:

Try to set z-index of ja-mainnav to -1.


/* Added by Bob  just to see */
.artgrandmenucontainer ul.dropdown li.hover, .artgrandmenucontainer
ul.dropdown li:hover {
z-index: 987654321;
}

#ja-search .artgrandmenucontainer ul.dropdown li.hover, ul.dropdown li:hover
{
z-index: 987654321;
}

#ja-search .artgrandmenucontainer ul.dropdown a.hover, ul.dropdown li:hover,
#ja-search  a.hover, #ja-search .artgrandmenucontainer a.hover, a:hover {
z-index: 987654321;
}

#ja-search {
z-index: 987654321;
}

Thx.  That sort of helps, however I checked further and anything at 9 or 
below fixes the top menu.  The side-effect is that this breaks the main menu.  
If I drop to 10 or below the mainmenu drop-down items get obscured by the 
slideshow and on pages where there is no slideshow, component containers.  
There seem to be a cascading series of z-index values that make the main 
navigation, slideshow and containers work together as a package.  How utterly 
convoluted.

test: http://www.dottedi.us/18

--
Bob Meetin
dotted i - http://www.dottedi.biz
LinkedIn: http://www.linkedin.com/in/bobmeetin
303-926-0167 (home/business)

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] What are the meanings of the arguments of border-image?

2011-12-26 Thread Peng Yu 
Hi,

It is not very clear to what exactly the arguments to border-image.

http://www.css3.info/preview/border-image/

The Working draft is not clear to me either. Could anybody help me
understand what the arguments mean? Thanks!

http://www.w3.org/TR/2002/WD-css3-border-20021107/#the-border-image-uri
-- 
Regards,
Peng
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] What are the meanings of the arguments of border-image?

2011-12-26 Thread Philippe Wittenbergh 

On Dec 27, 2011, at 7:28 AM, Peng Yu wrote:

 It is not very clear to what exactly the arguments to border-image.
 
 http://www.css3.info/preview/border-image/
 
 The Working draft is not clear to me either. Could anybody help me
 understand what the arguments mean? Thanks!
 
 http://www.w3.org/TR/2002/WD-css3-border-20021107/#the-border-image-uri

You're looking at a fairly old (and thus really outdated) text there.
Here is the latest version:
http://www.w3.org/TR/css3-background/#the-border-image

(in general, when reading specs it is a good idea to scroll to the top of the 
document and check that you see the latest version – follow the link 'latest…')

Now note that the border-image part of the spec is not well implemented in the 
release version of various browsers (and require vendor prefixes mostly).

I have a test case here, using the image used in the spec:
http://dev.l-c-n.com/CSS3_border-background/border-image1v2.html

To fully appreciate it you'll need either
* a very recent Gecko (Firefox - v12) nightly build - still requires a vendor 
prefix [1]
* recent  WebKit nightly builds - unprefixed [2]
* Chrome dev channel (17.0.963.12) - anyone can report how this works in Chrome 
16 ?

[1] http://nightly.mozilla.org/
[2] http://nightly.webkit.org/

Philippe
--
Philippe Wittenbergh
http://l-c-n.com/






__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] two drop downs / z-index / conflict

2011-12-26 Thread Philippe Wittenbergh 

On Dec 27, 2011, at 5:56 AM, Bob Meetin wrote:

 Thx.  That sort of helps, however I checked further and anything at 9 or 
 below fixes the top menu.  The side-effect is that this breaks the main menu. 
  If I drop to 10 or below the mainmenu drop-down items get obscured by the 
 slideshow and on pages where there is no slideshow, component containers.  
 There seem to be a cascading series of z-index values that make the main 
 navigation, slideshow and containers work together as a package.  How utterly 
 convoluted.

#ja-header { z-index: 11; } works on that page.

Aside: I was unable to access the submenus from the mainmenu. As soon as I move 
the mouse pointer to a submenu, it disappears.

Philippe
--
Philippe Wittenbergh
http://l-c-n.com/






__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] two drop downs / z-index / conflict

2011-12-26 Thread Bob Meetin 

On 12/26/2011 06:33 PM, Philippe Wittenbergh wrote:

On Dec 27, 2011, at 5:56 AM, Bob Meetin wrote:

Thx.  That sort of helps, however I checked further and anything at 9 or 
below fixes the top menu.  The side-effect is that this breaks the main menu.  
If I drop to 10 or below the mainmenu drop-down items get obscured by the 
slideshow and on pages where there is no slideshow, component containers.  
There seem to be a cascading series of z-index values that make the main 
navigation, slideshow and containers work together as a package.  How utterly 
convoluted.

#ja-header { z-index: 11; } works on that page.

Aside: I was unable to access the submenus from the mainmenu. As soon as I move 
the mouse pointer to a submenu, it disappears.

Philippe
--
Philippe Wittenbergh
http://l-c-n.com/


I think I have the disappearing submenu items on the main navigation fixed. If 
this is too muddled because of the complex structure of how the slideshow works 
in conjunction with the fancy of the inner box/divs, navigation and such I 
don't really want to waste people's time.

Were it doable the least complex solution would have been attaching a good 
z-index to the added art grand menu module.

I have a feeling that fixing this is going to take going through the logic of 
the default template stylesheet, finding the controlling z-index in a bunch of 
places, possibly also the slideshow stylesheet which is already more time than 
is allotted for the project.
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] Detailed browser compatibility of each css features?

2011-12-26 Thread Peng Yu 
Hi,

I'm not able to find a detailed browser compatibility table for each
css features (the following is just a high level table). Does anybody
know if there is a such detailed table?

http://www.findmebyip.com/litmus/

-- 
Regards,
Peng
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] Understanding the third argument of translate3d

2011-12-26 Thread Peng Yu 
Hi,

I thought that, among the 3rd google logo or the 4th google logo, one
should slip above the other should slip under the previous log,
because the z values are different. But both of them slip above the
previous logo. I guess that I still don't completely understand the
meaning of the third argument of translate3d. Could anybody help
understand it? Thanks!

!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
http://www.w3.org/TR/html4/loose.dtd;
html
  head
style type=text/css
  div {
position:relative;
left:200px;
top:200px;
-webkit-transition:2s;
  }
  div#x:hover {
-webkit-transform:translate3d(100px,0,0);
  }
  div#y:hover {
-webkit-transform:translate3d(0,100px,0);
  }
  div#-z:hover {
-webkit-transform:translate3d(0,-100px,-100px);
  }
  div#z:hover {
-webkit-transform:translate3d(0,-100px,100px);
  }
/style
  /head
  body
div id='x'
  px/p
  img src=http://www.google.com/intl/en_com/images/srpr/logo3w.png;
/div
div id='y'
  py/p
  img src=http://www.google.com/intl/en_com/images/srpr/logo3w.png;
/div
div id='-z'
  p-z/p
  img src=http://www.google.com/intl/en_com/images/srpr/logo3w.png;
/div
div id='z'
  p+z/p
  img src=http://www.google.com/intl/en_com/images/srpr/logo3w.png;
/div
  /body
/html


-- 
Regards,
Peng
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/