Den 15.07.2014 02:44, skrev Jon Reece:
> Maybe a pixel-rounding issue?
Yes, it is. Testing on various window-widths shows the gap come and go.
> Bumping the width of .l-region--navigation nav > .menu > li ul.menu
up to 100.5% appears to remove the unwanted separation in Chrome.
That, or to
2014-07-15 5:21, Crest Christopher wrote:
I have a vendor prefix for a placeholder for both Chrome and FireFox,
the same values for both, except FireFox displays a font-size of 3em
larger then Chrome ?
Please share your HTML and CSS code.
I tested with just
::-webkit-input-placeholder {
f
I have a vendor prefix for a placeholder for both Chrome and FireFox,
the same values for both, except FireFox displays a font-size of 3em
larger then Chrome ?
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.
Le 15 juil. 2014 à 10:37, Chris Rockwell a écrit :
> That will resolve the issue with the spacing, but the menu functionality is
> messed up -- `overflow` is not transitionable (?) so the sub menus appear
> before the transition finishes. See this pen for an example:
> http://codepen.io/anon
Works for me since you made the nav go all the way accross the page.
Mac OS Chrome 28.0.1500.71
Best,
Karl DeSaulniers
Design Drumm
http://designdrumm.com
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.or
>
>
> In that case, why not add 'overflow: visible' to
> .l-region--navigation nav > .menu:hover > li > ul
>
That will resolve the issue with the spacing, but the menu functionality is
messed up -- `overflow` is not transitionable (?) so the sub menus appear
before the transition finishes. See th
On Mon, Jul 14, 2014 at 5:16 PM, Chris Rockwell
wrote:
> I'm struggling to track down why, in Chrome (I'm in 35.0.1916.153 m), I'm
> getting transparent separation between some items. It's not occurring in
> Firefox or IE.
>
> The dev site is dev.truckingshow.com. To reproduce, simply mouse ove
Le 15 juil. 2014 à 08:30, Chris Rockwell a écrit :
> Thanks Jeff. Unfortunately, overflow:hidden is required, otherwise the sub
> nav items are always visible (you may not have noticed because the color is
> white). The goal is to have the menu transition height from 0 to X with
> css, so I ca
Thanks Jeff. Unfortunately, overflow:hidden is required, otherwise the sub
nav items are always visible (you may not have noticed because the color is
white). The goal is to have the menu transition height from 0 to X with
css, so I can't use display: none -> display: block either.
Chris Rockwel
I can't tell you why, but removing overflow: hidden from the style below
fixes it for me in chrome:
.l-region--navigation nav > .menu > li ul.menu {
display: block;
height: 0;
/* overflow: hidden; */
position: absolute;
width: 100%;
background: rgba(0, 54, 80, 0.97);
-webkit-transition: height 0.5
Hey all,
I'm struggling to track down why, in Chrome (I'm in 35.0.1916.153 m), I'm
getting transparent separation between some items. It's not occurring in
Firefox or IE.
The dev site is dev.truckingshow.com. To reproduce, simply mouse over any
of the main navigation items and you'll see a tran
You're fine
On Monday, July 14, 2014, Crest Christopher
wrote:
> I'm confused, I was using the for attribute;
> email
>
> ???
>
> Tom Livingston wrote:
>
> On Sun, Jul 13, 2014 at 7:05 PM, Robert A. Rosenberg
> wrote:
>
> At 14:08 -0400 on 07/09/2014, Tom Livingston wrote about Re: [css-d] P t
I'm confused, I was using the for attribute;
email
???
Tom Livingston wrote:
On Sun, Jul 13, 2014 at 7:05 PM, Robert A. Rosenberg
wrote:
At 14:08 -0400 on 07/09/2014, Tom Livingston wrote about Re: [css-d] P tag
can't be child of label ?:
If you wrap the input with the label, you can leav
On Sun, Jul 13, 2014 at 7:05 PM, Robert A. Rosenberg
wrote:
> At 14:08 -0400 on 07/09/2014, Tom Livingston wrote about Re: [css-d] P tag
> can't be child of label ?:
>
>
>> If you wrap the input with the label, you can leave off the
>> 'for' attribute (just read that... had no idea about that one!
14 matches
Mail list logo