On Sep 3, 2013, at 7:35 AM, Barney Carroll wrote:
> A portrait-oriented iPhone viewport is 320 (CSS) pixels wide, but the view on
> the right is 480 wide (the same as a landscape-oriented iPhone viewport). I
> don't know where the 530 came from.
ah..so my media breaks are incorrect…ok..thank
I have a 6-item menu which is inline at desktop sizes, but block at mobile
sizes. it works great, but at mobile, I'd like to have 2 columns of 3 buttons
to make better use of my vertical space. is there an easy way to do this? can
it even be done with css?
thank you!
John
existing desktop cs
On Aug 30, 2013, at 2:28 PM, Chris Rockwell wrote:
> It reaches 960 wide for me.
cool, but how so? I'm using an on-screen ruler that shows it as 860px!
Thank you!
John
__
css-discuss [css-d@lists.css-discuss.org]
http://www.
OK..I thought I had these things working but it appears not to be.
Right now, I am just trying to get 2 breaks to work right: desktop and mobile.
Yes, I know there are others but this is learning here just to get 2 of them to
work.
Seems the desktop one works, but the mobile does not. mobile sh
On Aug 30, 2013, at 2:02 PM, Chris Rockwell wrote:
> No, that is the problem. You commented out the opening of you tablet mq, but
> not the closing.
well that seems to have fixed one problem; the mobile MQ break to at least
happen. I see my 960 layout doesn't measure 960! I've got a wrapper
On Aug 30, 2013, at 1:22 AM, PL wrote:
> John,
> I think you need another media query in your css style sheet, you only
> have two, you probably need three: desktop, tablet and mobile.
Thank you, Patrice;
In working with my nav menu, one issue I'm having is getting the linked in icon
to line
On Aug 29, 2013, at 5:03 PM, Tom Livingston wrote:
> I would not be able to sleep tonight if I didn't bring up 'mobile
> first' again. It's been my experience with both methods, that it's
> easier to go from mobile up and usually requires less CSS. I've had
> some break point sheets with only a
On Aug 29, 2013, at 4:11 PM, "Tom Livingston" wrote:
> If you use the right MQs, you can still do that. Same concept, different
> widths and adjustments.
OK, wait..the lightbulb just went off..you're saying, whatever the "starting
point" is, requires no MQ; only the breaks do, and those are
On Aug 29, 2013, at 4:06 PM, "Tom Livingston" wrote:
> Might be simpler to not have an MQ around your desktop since in this case
> it's your base. And just make adjustments in the other MQs. No need to repeat
> everything.
well that is a very good idea, Tom. Right now, my Desktop is 960, but
OK..I may have solved at least part of it…
for my desktop query, I either deleted or failed to type the closing } for the
media query!
watch this space…
John
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.o
On Aug 29, 2013, at 3:41 PM, Tom Livingston wrote:
> Try using min-width instead.
that fixes it to tablet size and no larger!
I do see ppl using various combos of min- and max-width…must be something else
weird in my code.
J
__
Can't look right now but are you adding to or changing desktop styles or
> replacing them. Are you working desktop down?
> —
> Sent from Mailbox for iPhone
>
>
> On Thu, Aug 29, 2013 at 6:20 PM, John A. Johnson
> wrote:
>
> I am trying to get solid on basic m
I am trying to get solid on basic media queries with the simple site, link
below. When narrow the viewport to "tablet" which I have set at
max-width:768px, the desktop styles vanish, but tablet styles don't take their
place. I've been wracking my brain over this and I am not seeing the problem.
Is there a way to impose flexibility in font sizes, such as when viewport
shrinks, designated type sizes also decrease by a controllable amount?
what I have for my font-size right now is a %, shown below, but that is % of
the parent type not of the parent tag. Images scale down, yet my headings
On Jun 27, 2013, at 11:14 AM, Philip Taylor wrote:
> Elements have certain
> default renderings which they acquire from the browser, but
> they do not /inherit/ those renderings from the browser in
> the CSS sense of "inherit".
OK..I get it. that is an important distinction...
_
On Jun 27, 2013, at 10:54 AM, Philip Taylor wrote:
> As the browser is not an element in the document tree, the
> element cannot inherit any properties from it. It may well acquire
> them in some other way, but this is not inheritance /qua/ inheritance.
Isn't it the case that browser default
16 matches
Mail list logo
