Sent from losPhone
> On Nov 11, 2013, at 8:52 PM, Philippe Wittenbergh wrote:
>
> Another one: Apple mouse through history — in CSS:
>
> http://codepen.io/joshbader/full/fKjra
>
>
>> I need to get out more.
>
> Hmm, it is bloody cold outside - I’ll stay by the stove :-(, maybe do a
> litt
Le 12 nov. 2013 à 02:33, Theresa Jennings a
écrit :
> Deconstruct at your leisure.
>
> http://pattle.github.io/simpsons-in-css/
>
> I had no idea CSS could do this.
Another one: Apple mouse through history — in CSS:
http://codepen.io/joshbader/full/fKjra
> I need to get out more.
Hmm, it
On Nov 11, 2013, at 11:33 AM, Theresa Jennings wrote:
Deconstruct at your leisure.
http://pattle.github.io/simpsons-in-css/
I had no idea CSS could do this. I need to get out more.
__
css-discuss [css-d@lists.css-discuss.org
11 nov 2013 21.38 Chris Rockwell:
> I see your point MiB. I was trying to make the point that fluid design
> responds to the screen size, adding in breakpoints only enhances that
> response.
Yes, that's currently how I do it technically too, but it's of course just a
set of possible technique
I see your point MiB. I was trying to make the point that fluid design
responds to the screen size, adding in breakpoints only enhances that
response.
On Mon, Nov 11, 2013 at 3:36 PM, MiB wrote:
>
> 11 nov 2013 21.06 Chris Rockwell:
>
> > responsive design is fluid design
>
>
> I do think that
11 nov 2013 21.06 Chris Rockwell:
> responsive design is fluid design
I do think that here a better term, than "fluid" design, is "adaptive" design,
which means the design will adapt to the context. "Fluid" leads the thought to
a specific set of design techniques, which do not give the comple
On Mon, Nov 11, 2013 at 2:37 PM, Colin (Sandy) Pittendrigh
wrote:
> I'm a beginner at responsive design. I understand the mobile first
> argument which (at least from the client side) boils down to "Design for
> the phone first and then use CSS media queries to vary floats and widths as
> needed,
This could be a much longer discussion, but it sounds like your big picture
view is a bit flawed from the onset. Responsive design isn't about coding
for devices, it's coding for screen sizes (albeit with special code for
browsers on those devices). And, responsive design is fluid design. But
in
I'm a beginner at responsive design. I understand the mobile first
argument which (at least from the client side) boils down to "Design for
the phone first and then use CSS media queries to vary floats and widths as
needed, and to use javascript to add non-essential images on the fly, for
larger m
On Mon, Nov 11, 2013 at 1:23 PM, Hahnel, Fred (DET-MRM)
wrote:
> we don't use tags at all. This suddenly started after the 'upgrade' to
> Outlook 2013 web server last Thursday. As I said before, old emails that
> were rendering properly before this upgrade, now also show the unwanted blank
we don't use tags at all. This suddenly started after the 'upgrade' to
Outlook 2013 web server last Thursday. As I said before, old emails that were
rendering properly before this upgrade, now also show the unwanted blank spacing
-Fred Hahnel
-Original Message-
From: Tom Livingston
On Mon, Nov 11, 2013 at 12:24 PM, Hahnel, Fred (DET-MRM)
wrote:
> I am encountering a strange issue with Outlook Web Access (OWA). We recently
> upgraded the server to Outlook 2013, was Outlook 2007.
> Previous emails with stacked tables now have a blank line between each table.
> We are also
Deconstruct at your leisure.
http://pattle.github.io/simpsons-in-css/
I had no idea CSS could do this. I need to get out more.
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List w
I am encountering a strange issue with Outlook Web Access (OWA). We recently
upgraded the server to Outlook 2013, was Outlook 2007.
Previous emails with stacked tables now have a blank line between each table.
We are also seeing this now on older emails that rendered properly on OWA with
the o
14 matches
Mail list logo
