Re: [css-d] Role of Pre-processors

maj 10 2014 16:54 Tim Climis : > but those are irrelevant to > this thread. How did standards enter into a discussion on the role of (CSS) preprocessors anyway? Preprocessors are largely operationally independent of standards — you may choose to support them or not as usual — so I feel the ro

Re: [css-d] Role of Pre-processors

maj 10 2014 12:54 Philip Taylor : > I respectfully disagree. The problem is not what the developers > /want/ us to do, but rather than there are far too many of us > who are only too eager to accede to their wishes. We are under no > obligation whatsoever to do anything that a developer might w

Re: [css-d] CSS menu at 320px -- meta offtopic

apr 27 2014 18:34 Tom Livingston : > Perhaps I'm using "list" in a more general term. Someone *on* the list > has been compromised. And you are correct, it is difficult to figure > out where it's coming from. My main point was that I don't get these > messages outside of this list. While the me

Re: [css-d] Firefox and page inflation -- late response

29 apr 2014 kl. 18:35 skrev Tom Livingston : > I recall seeing this come through, I thought so to but couldn’t find it my mailbox nor in the online archive. > but anyway, I'd like to say that I wasn't defending *not* using RWD, I'm a > big proponent of it, but IIRC there were some replies that

Re: [css-d] IE 10 issue

apr 27 2014 20:12 Eric : > I don't think running IE 9, 10 or 11 is a good idea right now until they fix > the > new security bug issue that was announced > > Here's a short article about it >

Re: [css-d] Ready for Pre-processors?

apr 27 2014 12:18 Jens O. Meiert : > Just following with one ear but why would that be irrelevant? Read the OP. __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http:

Re: [css-d] Ready for Pre-processors?

apr 26 2014 00:36 Reese : > > CSS pre-processors do not write optimized code by default, it is very > easy to write code that will result in bloat and reduced performance. > It didn't take much Googling to find this article: > >

Re: [css-d] Ready for Pre-processors?

25 apr MiB : > I didn’t get the original for this. Eric? Andrews original was found in the spam folder for unknown reasons. __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d L

Re: [css-d] Ready for Pre-processors?

I didn’t get the original for this. Eric? apr 25 2014 03:21 John Johnson : > certainly seems appropriate to me…I’d vote “yes” for the powers that be to > consider. I’m for it as long as there is a clear connection to CSS, which there typically is. __

Re: [css-d] Sticky Footer Problems

apr 22 2014 01:14 MiB : > > apr 21 2014 21:37 Jennifer : > >> It seems that there should be a way to 'fix' this. I know it works, since >> I've tried it on a simple page, so it looks like I'll have to start >> stripping out other CSS t

Re: [css-d] Sticky Footer Problems

apr 21 2014 21:37 Jennifer : > It seems that there should be a way to 'fix' this. I know it works, since > I've tried it on a simple page, so it looks like I'll have to start stripping > out other CSS to see what's interfering with the footer. And I thought this > was going to be a simple tas

Re: [css-d] Media Queries: How many pixels make an em ?

apr 19 2014 16:00 Tedd Sperling : > > 4. Lastly, use ems for images as well. That way your entire site scales well > with zooms. Here's my write-up on it: The downside is unacceptable to me, as ems for image width doesn’t respect "zoom only text”. I’d use percentages for width instead. ___

Re: [css-d] Firefox and page inflation

get” the need to design at the content level, at least not when they are doing the content. It’s possible I need to find people to work with that can do content so I can focus on server-side and interface design. /MiB __ cs

Re: [css-d] Firefox and page inflation

apr 10 2014 16:19 Davies, Elizabeth : > the Mobile First philosophy brought many "wins" with it. Perhaps the name is > misleading and it should be "Simplicity First" or "Basics First" ;D I liked that one. __ css-discuss [css-d

Re: [css-d] Firefox and page inflation

apr 102014 12:36 Georg : > I agree in principle, but guess how much you "play by the market", or not, > depends on whether you are trying to sell something, or not. :-) > > FWIW, I have no "first" in mind when designing, only "all"... > http://www.gunlaug.com/contents/design/mobile-first.html

Re: [css-d] Font-Sizes - Golden Rule ?

apr 9 2014 08:48 Karl DeSaulniers : > Looks like there are some exceptions. Have a look see... > There ARE a few that took on the browser width, but the majority stuck with > their parent. > > http://designdrumm.com/percentage_test.html Which are the exceptions you mean? _

Re: [css-d] Floating Window

mar 28 2014 15:52 D Mark Weiss : > Some of the implementations that I have seen kind of have a black or greyed > out border and in the top right corner have an "X" for closing the floating > editing window. That sounds like the good ol’ lightbox technique. Lightboxes can be used for many thi

Re: [css-d] dealing with media breaks

mar 26 2014 17:54 Philip Taylor : > "Testing can reveal only the presence of bugs, not their absence" > > -- Edsger Dijskstra (11 May 1930 – 6 August 2002) Edsger was an avid tester was he? An automated test written to get rid of a specific bug, does indeed prove that this specific bug with th

Re: [css-d] Responstable SCSS

mar 17 2014 20:21 SSC_perl : > I almost hate to ask this, but would it be possible for someone to test my > page on an Android phone to make sure it works? Unfortunately, everyone I > know has an iPhone. I haven’t verified the trustworthiness of these, but useful for a quick look: https://ww

Re: [css-d] display:inline-block differences in browsers

mar 17 2014 08:35 MiB : > mar 17 2014 05:10 John : > >> I think I'm getting closer to understand how to use this new (to me) method >> of positioning, but I don't get what it's relative to, such that Firefox >> renders it differently from Opera, Chrome

Re: [css-d] display:inline-block differences in browsers

mar 17 2014 05:10 John : > I think I'm getting closer to understand how to use this new (to me) method > of positioning, but I don't get what it's relative to, such that Firefox > renders it differently from Opera, Chrome and Safari.. Absolute positioning is relative to the nearest Positioning

Re: [css-d] Do modern mobile browsers deliberately ignore font size?

mar 13 2014 23:02 MiB : > mar 13 2014 Ezequiel Garzón : > >> http://81.4.104.136/fonts.html > > > I don’t see your issue in Android nor in IOS. Anyone else? I have now tested this page on several other Android hand sets and the text sizes of both the elements are t

Re: [css-d] Do modern mobile browsers deliberately ignore font size?

mar 14 2014 00:24 L. David Baron : > On Sunday 2014-03-09 21:52 +0100, Ezequiel Garzón wrote: >> Is this font boosting/inflation? > > It sounds like it is. Could it be that only certain android versions are affected? I’ve never encountered this issue on any platform before. I also have never h

Re: [css-d] Do modern mobile browsers deliberately ignore font size?

mar 13 2014 Ezequiel Garzón : > http://81.4.104.136/fonts.html I don’t see your issue in Android nor in IOS. Anyone else? __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki

Re: [css-d] Do modern mobile browsers deliberately ignore font size?

mar 12 2014 22:07 Ezequiel Garzón : > I specified in my example td,p { font-size: medium }. I would hence expect > the font size in my very simple table and in my single paragraph to be the > same, whether I include a meta viewport tag or not. It turns out it only > happens in modern Android b

Re: [css-d] Do modern mobile browsers deliberately ignore font size?

mar 10 2014 21:54 Ezequiel Garzón : > I again feel font size in particular is not supposed to be > affected by this meta tag Feel? Incongruent with something (what?) would seem more appropriate. Case in point? __ css-discuss [

Re: [css-d] rotate image CSS3?

Jon Reece : > Since transform is still an experimental feature of CSS3, you'll need to > use vendor prefixes: > > .tilt-2d { > -webkit-transform: rotate(25deg); > -moz-transform: rotate(25deg); > transform: rotate(25deg); > } > > The reason the codepen example works without them is because t

Re: [css-d] Will the unsemantic HTML elements B and I be soon phased out?

feb 17 2014 18:51 Micky Hulse : > Ya'll, I hate to be rude, but isn't markup debates a little OT for CSS-d? Actually it is indeed OT, except for where it ties in directly with CSS. References to external discussions on the topic are not OT, IMHO. So good point.

Re: [css-d] Will the unsemantic HTML elements B and I be soon phased out?

17 feb 2014 kl. 18:35 skrev Richard Grevers : > But if the differentiation > of such text matters, it makes sense to use markup that will differentiate > it regardless of the availability of CSS. A valid point. > In most cases this is or > , often with a class to classify it semantically. Wi

Re: [css-d] hiding things and bandwidth?

MiB : > the choices a developer will have to make is about a complete system rather > than individual solution. > Solutions obviously. Sorry about that. /MiB __ css-discuss [css-d@lists.css-discuss.org] http:

Re: [css-d] hiding things and bandwidth?

feb 17 2014 18:05 Colin (Sandy) Pittendrigh : > So > at higher big picture level some discussion about how CSS fits into the > overall scheme of things still seems appropriate. Exactly. > Using Javascript cookies and (initially) a double GET to determine the > state of the current user agent ma

Re: [css-d] hiding things and bandwidth?

ices a developer will have to make is about a complete system rather than individual solution. /MiB __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http

Re: [css-d] hiding things and bandwidth?

feb 15 2014 06:22 Chris Williams : > And how do they do that? How does the server know the user's page width? > By their going to m.example.com as opposed to example.com. Or with JS… Javascript analysis of screen type will take care of a majority of users and feed the relevant data to the ser

Re: [css-d] Will the unsemantic HTML elements B and I be soon phased out?

feb 16 2014 23:49 Andrew Cunningham : > The problem with and is that HTML5 gives them semantic meaning but > they also have inherent styling. How is that different from any semantical element? > > Of I use these elements in a multilingual envirnonment, then for some > languages I would need

Re: [css-d] Perhaps a simple solution...

17 feb 2014 kl. 08:33 skrev MiB : > You could also use microformats and make it a part of a hcard (look some text fell off there. It should be: "You could also use microformats and make it a part of a hcard (look up microformats and hcard at and here too: microformats.org/wi

Re: [css-d] Perhaps a simple solution...

feb 17 2014 03:43 Alan L.S. Steytler : > ...but I don't have it. > > http://robertgarritylaw.com/Alt_index.html > > The image should stand by itself, centered, with the succeeding text below. > Viewed in various devices, and various browsers, it's all over the place. Center the image in your

Re: [css-d] hiding things and bandwidth?

feb 14 2014 19:59 Chris Williams : > that's Javascript, and while a worthwhile topic and > a useful method used more and more lately, it's off-topic here. Solves > several of the issues with separate sites, but adds another language, > testing, and layer of complexity. I fail to see how servi

Re: [css-d] How to align one word left and another word right in a select list without giving each its own class, div or style (and without using a monospace font)

jan 19 2014 21:38 Larry Martell : > In my example, in the first option, I would need 12S left justified > and by_target right justified. You’re very likely to need a javascript solution, I think. There is one discussion concerning this problem here: http://stackoverflow.com/questions/4497688/

Re: [css-d] How to align one word left and another word right in a select list without giving each its own class, div or style (and without using a monospace font)

19 jan 2014 kl. 21:47 skrev Philip Taylor : > first-word is not a functional nor valid css pseudo element, is it? So…? __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FA

Re: [css-d] Stylesheet weight

jan 17 2014 15:58 Tom Livingston : > As an example, i've got 8 page templates well under way and my > minified sheet is 23k. Does that sound bad? You have only text content an no media files? It’s the total weight that counts after all. What’s the totals? And if different, where it is different

Re: [css-d] child problems with li?

dec 21 2013 03:18 John : > am I right thinking this is an inheritance issue? the descendent "nav li” selector will of course affect all such elements unless you override them. The "footer li” selector at the linked page overrides the display and font-size of ”nav li". Relative font size is bas

Re: [css-d] Visual styling vs. source order

dec 20 2013 20:15 Greg Gamble : > Pages should have headers in order, with one H1 on top. I disagree. In html5, it's perfectly correct to sectionalize different parts of the content and have a new header structure within each section with a top H1 per section element and following headers. Th

Re: [css-d] Visual styling vs. source order

dec 202013 01:16 Rick Gordon : > I think a good criterion is this: If you were looking at the content, in an > undesigned, purely logical order, what order would the code fall in? Since this is headings these should make sense in an HTML5 outliner like this one http://gsnedders.html5.org/outl

Re: [css-d] trying to use CSS to define width of Google search input box

dec 14 2013 22.38 Angela French: > I figured it out. I had to discover how google was referencing the input. One nice way to discover this is to use the built-in developer tools in Firefox. I suppose other browsers also have developer tools that gives this functionality, but I always start in

Re: [css-d] CSS Progress Bar Help

We're supposed to see a progress bar at this link? http://www.surfshopcart.com/cgi-bin/demos/2/shop.cgi I'm sorry, but I don't have time to look around for what is the problem and I'd assume this applies to many other people as well. Present the issue if you want help. Why don't do a focused e

Re: [css-d] "display:none" on android browser will prevent "click" event?

dec 4 2013 16.17 Chris Rockwell: > That being said, this seems like a case > where you'd want to use something like 'visibility:hidden' or 'hidden' or > http://snook.ca/archives/html_and_css/hiding-content-for-accessibility. > That should make it accessible and it works on an android browser (sto

Re: [css-d] Inspect phone from desktop

1 dec 2013 kl. 22.56 skrev Karl DeSaulniers: > Sorry. Didn't read an article. I plugged in my iPhone and when I went to go > inspect a page in safari, I saw a menu option with my phones name. Hovered > over it and it said no device page found or something like that. So I then > opened safari

Re: [css-d] Inspect phone from desktop

1 dec 2013 kl. 09.32 skrev Karl DeSaulniers: > Didn't know if you all knew this but evidently in Safari 6.1 (on Mac as far > as I know) when you have your phone plugged into your computer (i am using an > iPhone 5) and a webpage displaying on your phone, you can now inspect the > webpage on yo

Re: [css-d] Chrome for Mac disowns children

nov 19 2013 15.10 Barney Carroll: > On 19 November 2013 14:01, MiB wrote: > I can't vouch for hover as I don't see this element to begin with in Chrome > 31. > > That's very interesting. This is what I get: > http://www.youtube.com/watch?v=QNyGy47YNHc It s

Re: [css-d] Chrome for Mac disowns children

nov 19 2013 14.55 Barney Carroll: > David has discovered a bug in Chrome 31 whereby rules featuring > concurrent positioning pseudo-classes on the same element are removed from > the DOM when the affected element is hovered. I can't vouch for hover as I don't see this element to begin with in

Re: [css-d] Chrome for Mac disowns children

18 nov 2013 kl. 05.11 skrev David Hucklesby: > While this works in modern browsers, the marker disappears in Chrome v.31.0 > for > Mac. In this simplified Pen, it disappears on :hover. With slightly more > complex > CSS it does not appear on Chrome at all. (Okay on Chrome for Windows.) David,

Re: [css-d] Chrome for Mac disowns children

nov 18 2013 05.11 David Hucklesby: > If you have Chrome on a Mac, I'd be grateful if you let me know whether you > see > this phenomenon. Could be something to do with my install (on Mavericks, > FWIW). Works in Chrome 29. _

Re: [css-d] aligning some text in td at bottom

> > On Nov 16, 2013, at 4:05 PM, Chris Rockwell wrote: > >>> >>> >>> Except that to position the link inside the table cell isn't the only >>> solution, Why not on a new row for instance? Why must the link belong on >>> the exact same row? I don't see that. >>> >> >> Should the link not ap

Re: [css-d] aligning some text in td at bottom

nov 16 2013 18.07 Chris Rockwell: > The JavaScript is necessary in Chris' solution because the height needs to be > set in something other than percentage or auto to get the added element (div > or otherwise) to fill the td vertically. > > Good catch. > I agree that in some cases it could be

Re: [css-d] aligning some text in td at bottom

16 nov 2013 kl. 01.23 skrev David Hucklesby: > Glad you got some JavaScript that works, Sara. Here's Chris Coyier's solution: > > Great! This is what I imagined as a potential start point for a solution, However, To foreg

Re: [css-d] The Simpsons in CSS

15 nov 2013 kl. 15.51 skrev Jon Reece: > Not really an illustration app, but Macaw's tagline is "Stop writing code. > Start drawing it." > > http://macaw.co/ Ahhh, and you tell us now. This really looks like the real [whatveryourcurrentdevelopmentapp]-killer. At least all of those dreadful "

Re: [css-d] aligning some text in td at bottom

nov 14 2013 23.12 Karl DeSaulniers: > Which is highly unlikely now a days or I should say most of the people that > are part of a target market one would direct to will not be disabling it. I > think it is also safe to say the vast majority of people don't even know how > to turn it off nor th

Re: [css-d] aligning some text in td at bottom

nov 14 2013 14.43 Sara Haradhvala: > I ended up using JavaScript to set the height of each cell - that seems to > work in all browsers! In theory, if no-one is using a browser with javascript turned off. __ css-discuss [css-d

Re: [css-d] The Simpsons in CSS

nov 13 2013 06.30 Theresa Jennings: > I think they're more proof of concept than anything else. Of course, but what about in three years? Someone will always be going there first. __ css-discuss [css-d@lists.css-discuss.org]

Re: [css-d] The Simpsons in CSS

12 nov 2013 kl. 22.39 skrev Tim Arnold: > > I think impressing was the main goal. That, and to an an exercise in "what > if?" So how difficult would it be to implement CSS in a graphics app you think? I'd say it's doable. If it's an attractive feature today I'm not sure. But it could of cou

Re: [css-d] The Simpsons in CSS

nov 12 19.14 COM: > This is cool and all, but…seriously, is CSS being touted as an illustration > tool? > Am I missing a concept here? If it's possible someone will make it a part of an illustration software tool. My guess would be not Adobe. > > I am very impressed by the samples shown… Bu

Re: [css-d] Trying to get the big picture view on responsive design

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

Re: [css-d] Trying to get the big picture view on responsive design

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

Re: [css-d] z-index issue on iOS

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

Re: [css-d] z-index issue on iOS

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

Re: [css-d] z-index issue on iOS

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

Re: [css-d] z-index issue on iOS

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

Re: [css-d] Flexbox order and first/last elements ...

26 oct 2013 17.01 Colin (Sandy) Pittendrigh: > Or is there a current benefit--that's worth the effort--of using the new > stuff now? Always embrace the latest browsers and work with that, simply giving older browsers another experience. You can also use poly-fils to some extent while the older

Re: [css-d] Start at the bottom! (was "Front page breaking in IE8, maybe 9 too")

9 oct 2013 18.23 Philip Taylor: > I sent the following two replies off-list, but as our esteemed > leader has not ruled the discussion off-topic, I repeat > them here so that all points of view may be considered. I guess it's your kind of common courtesy to repost private email correspondence t

Re: [css-d] Start at the bottom! (was "Front page breaking in IE8, maybe 9 too")

9 okt 2013 16.28 Karl Snyder: > Also, chopping the heck out the original post might make it impossible for > those who are not keeping the current thread in the brains, from knowing > exactly what you are taking about. Well, leaving an unedited mess below your response forcing the user to scrol

Re: [css-d] Start at the bottom! (was "Front page breaking in IE8, maybe 9 too")

9 oct 2013 14.25 Eric A. Meyer: > whatever your reply style, you trim the quoted material to include only that > which is relevant and absolutely necessary to your reply, and no more. This trimming is central to make any response fully available. One may ask since when great designers does n

[css-d] Start at the bottom! (was "Front page breaking in IE8, maybe 9 too")

What's up with the top posting from people like Chris Rockwell, Tom Livingston, Karl Desaulniers and Theresa Jennings (a few). I'm usually quite tolerant to this, but I quickly lost interest in the problem and any solutions when usage of this was as widespread as in this thread. The ideal is if

Re: [css-d] Container Div

1 oct 2013 19.42 Tom Livingston: > This is a viable solution under the right circumstances. And just what did I just say? The solutions I linked to are worse, are they? __ css-discuss [css-d@lists.css-discuss.org] http://www.cs

Re: [css-d] Container Div

1 okt 2013 19.33 Chris Rockwell: > I see, I did type "margin: 0 auto" in the email. David pointed this out, but > when I checked I **only** checked the pen, I didn't go back in the email to > double check. It should be: Yes, thanks this helped. I guess I missed that part as I always have 0

Re: [css-d] Container Div

1 okt 2013 15.10 Chris Rockwell: > If absolute positioning is an option, a simple, clean way is: > > .centeredElement { > position: absolute; > margin: 0 auto; > left: 0; > right: 0; > top: 0; > bottom: 0; > height: 300px; > width: 300px; > } Ok, so now I tried this with only t

Re: [css-d] Container Div

1 okt 2013 kl. 16.22 skrev Chris Rockwell: > What version? It's fine in 29.0.1547.76 m and 32.0.1657.2 canary Aura Chrome 29.0.1547.65 on Mac. Height isn't respected. Also, what happens if height is an unknown and the box needs to accommodate different content?

Re: [css-d] Container Div

1 okt 2013 kl. 16.16 skrev Chris Rockwell: > What browser are you viewing in? It works for me in ff,chrome,ie10 It fails in Chrome. __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d L

Re: [css-d] Container Div

1 okt 2013 15.10 Chris Rockwell: > If absolute positioning is an option, a simple, clean way is: > > .centeredElement { > position: absolute; > margin: 0 auto; > left: 0; > right: 0; > top: 0; > bottom: 0; > height: 300px; > width: 300px; > } > > http://codepen.io/chrisrockwell/

Re: [css-d] Container Div

1 okt 2013 13.24 Karl DeSaulniers: > Last question for now. In your resizing box example, > how would you get the text to scale with box, as well as, > say an image and another div with an image in it? > > Is there a css way to do this besides zoom like a scale or transformMatrix or > is zoom

Re: [css-d] Container Div

1 okt 2013 kl. 12.29 skrev Karl DeSaulniers: > What is using a # before a property called? Like this line in your code. > What are you doing here? Sorry for any elementary questions, It's fallback css for browsers that don't acknowledge display:table. There are many levels to understand with

Re: [css-d] Container Div

1 oct 2013 12.09 Karl DeSaulniers: > Great example! Thank you. > I'm a little dizzy now though. :) > > I have usually done my centering with top: 50% left: 50% and negative margins > on one div. > Is this not a standard way of accomplishing this? I noticed you used 3 divs > for centering. > Is

Re: [css-d] Container Div

1 okt 2013 11.25 Karl DeSaulniers: > Can anyone help me? I am looking to create a DIV that is centered > horizontally and vertically in the window and inside this div I have images > and text and the like. I want the images and the text to stay inside this > div. How can I go about this? Vie

<    1   2