Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Ask Håkon About CSS or...?

Posted by Roblimo on Tue Jun 20, 2006 12:31 PM
from the partly-to-blame-for-web-2.0 dept.
Back in 1994, while working for the World Wide Web Consortium (W3C), Håkon Wium Lie (pronounced more or less "how come") proposed the idea of Cascading Style Sheets (CSS). Got a CSS question? An Ajax question? Want to know why Håkon loves Free Software so much? Or something else, related or not? Go ahead and ask -- after checking some of the links above, so you don't duplicate questions he's answered in other interviews or in articles he's written. (One question per post, please.) We hope to post his answers Friday.
+ -
story

Related Stories

[+] Håkon Responds to Questions About CSS and... 204 comments
You submitted questions for Håkon Wium Lie on June 20. Today we have his answers, not only to the (+5 moderated) questions we sent him, but to a bunch of others he thought would also be interesting to answer.
[+] Microsoft's IE Team Leader Answers Slashdot Questions 530 comments
We got lots and lots of questions for Dean Hachamovitch, whose formal title is "general manager Internet Explorer at Microsoft Corp." Picking a mere 10 of those questions was not easy, and I wish Dean could have answered twice as many -- and so does he, but his schedule has been tight this week. Anyway, here are his answers to the Chosen Ten.
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Stick_Fig (740331) on Tuesday June 20 2006, @12:35PM (#15570656) Homepage
    ...validate? :D
  • by iceborer (684929) on Tuesday June 20 2006, @12:37PM (#15570678)
    Want to know why Håkon loves Free Software so much?

    Well...Håkon?
  • Why? (Score:5, Funny)

    by Anonymous Coward on Tuesday June 20 2006, @12:37PM (#15570679)
    Free software is destroying american jobs. Why do you hate america?
  • Where... (Score:3, Interesting)

    by aleksiel (678251) on Tuesday June 20 2006, @12:40PM (#15570708)
    Where is CSS going in the future? Expecting anything in particular for CSS4, or will we never reach it?
        • Re:Where... (Score:5, Interesting)

          by bcat24 (914105) on Tuesday June 20 2006, @02:36PM (#15571627) Homepage Journal
          CSS 3 *is* far into the future. :) It won't be a rec. for a long time, and it won't be supported by browsers (IE, I'm looking at you) for an eon.

          OK, here's my related question:

          Do you think the W3C development process is too slow? I know that you guys want everything to be perfect, but it seems to take far longer than necessary. CSS 3 shows promise and I wouldn't want it to die a slow death in standardization.
  • Opera (Score:5, Interesting)

    by taskforce (866056) on Tuesday June 20 2006, @12:41PM (#15570717) Homepage
    Opera 9.0 seems to offer a lot of decent additions to Opera's standards pool. How satisfied are you personally with the work the team has done on implementing standards, and is there anything in there you feel is superflous and anything you would have preferred to see which wasn't in there?
    • Opera 9.0 seems to offer a lot of decent additions to Opera's standards pool. How satisfied are you personally with the work the team has done on implementing standards

      Translation: I like Opera, please give them your blessings so that I may sleep at night.
  • I have one (Score:3, Funny)

    by linvir (970218) * on Tuesday June 20 2006, @12:42PM (#15570725)
    Why do you love Free Software so much?
  • Padding (Score:5, Interesting)

    by Anonymous Coward on Tuesday June 20 2006, @12:43PM (#15570732)
    Why was the decision made to make padding apply outside of the width of a 'box', rather than inside, which would seem to make more sense?
    • Re:Padding (Score:5, Interesting)

      by Anonymous Coward on Tuesday June 20 2006, @01:01PM (#15570867)
      In addition: Was an concideration given to the effect that this would have on blocks using percentages for sizes? Is any concideration being given to fixing the problems that this causes?
    • Re:Padding (Score:5, Informative)

      by pikine (771084) on Tuesday June 20 2006, @02:27PM (#15571576) Journal
      Space inside the box is the "padding," while space around (outside) the box is the "margin." Between "padding" and "margin," there is also a "border." I'm not sure if asking how the terminology is determined is very interesting.
  • Go ahead and ask -- after checking some of the links above, so you don't duplicate questions he's answered in other interviews or in articles he's written.

    Duplicates? On Slashdot? Surely you jest, sir!

  • by 1155 (538047) on Tuesday June 20 2006, @12:44PM (#15570738)
    CSS is a great idea, separating content from everything else. My problem with it is that it's such a horrendous beast of a thing to implement. For instance, there's nothing really good for say, putting something into "the middle" from what I can find. Now if there is, fine, don't make this question about the example. There are literally hundreds of design decisions that feel like they were implemented in a way to just make things as difficult as they can be.

    Why is CSS such a pain compared to other languages?
    • by mini me (132455) on Tuesday June 20 2006, @01:10PM (#15570937)
      Why is CSS such a pain compared to other languages?

      It's really not that bad once you get on to it. It would be nice if it could do math to calculate positions/sizes/etc., and supported multiple backgrounds for a single element, ala Safari. But all in all, it's poor browser support that really makes CSS difficult.
      • People used tables for layout because it was the easiest way to center things - and it worked well if you made sure all your tags were nested and closed correctly. Then along comes CSS, and tables are taboo for layout (and for some good reasons, too)...

        But there are cases where CSS cannot perform layout as well as tables. One of the reasons is because you can center a table that is sized to fit the content. In other words, in CSS you need to specify the size of the container in order to "auto" the margin
    • Because CSS is based on many misunderstandings:

        - You are supposed to separate content and visual elements. An input is both.

        - An HTML page has to be XML. To achieve this part of positioning is delegated to attributes.

        - The belief that tables are bad. In fact they are very intuitive elements - unlike the DIVs. It would have been much better if we could do with one block element that had the strong points of both tables and divs.

        - A total disregard for consistency. Every HTML page contains 3 languages for the same thing: HTML, CSS and javascript. In many cases all three use slightly different names for the same thing. It would have been much better if they had been integrated into a consistent interface.

      My question for Hakon: HTML became popular because it was so simple to use that everyone could use it. CSS by contrast is so complicated that only fulltime professionals understand it. Will CSS stay an elite thing?
    • by rar (110454) on Tuesday June 20 2006, @04:57PM (#15572617) Homepage
      ... There are literally hundreds of design decisions that feel like they were implemented in a way to just make things as difficult as they can be.

      I'd like to try to turn your observation into a more specific question:

      CSS is clearly very useful for separating style from content. But apparently people tend to have problems when using it for layouts. Would you say this is because people have not yet understood how to properly do layout in CSS, or is it CSS that is lacking in this area? What can be done to improve the situation? --- Would the web benefit from HTML and CSS being complemented with some kind of "layout language"?
      • Not only does that only center horizontally, it doesn't even work in all browsers!

        Vertical centering is just as important. I want to be able to (without tables) place a 500x500 box center of the window without resorting to some wierd javascript to do it. You give me a div (or p) that does this in all browsers with zero javascript and I will be impressed.

        Browser support is the other issue, and it is a killer.

        That said, I love the concept and most of methods, I just hate the browser wierdness.
        • Vertical centering is just as important. I want to be able to (without tables) place a 500x500 box center of the window without resorting to some wierd javascript to do it. You give me a div (or p) that does this in all browsers with zero javascript and I will be impressed.

          The way I usually do it is with negative margins. It's kind of a workaround, but it does work. Position the div 50% from the top and left, and then give it a negative margin-top & margin-left equal to 1/2 its own height & width respectively (in the case of 500x500, use a -250px margin) and it should center vertically.

          For example, I use something like this on one of my sites:
          #container {
          position: absolute;
          left: 50%;
          top: 50%;
          z-index:1;
          width: 500px;
          height: 500px;
          margin-left: -250px;
          margin-top: -250px;
          }

  • by gaspar ilom (859751) on Tuesday June 20 2006, @12:46PM (#15570752)
    1.) What do you think of XSLT?

    2.) Would it be crazy to have CSS incorporate data selection and assembly? (using something like XPath -- alowing more complete segration of data and formatting.)
  • I always wanted to have "included" substyles or "aliases" in my CSS definition, to save redundancy.

    (For includes)
    .class1 { color:#ff0000; }
    .class2 { background-color:#ffffff; }
    .class3 { include:class1,class2;font-weight:bold; }
    (For aliases)
    @alias color1 #ff0000;
    @alias color2 #ffffff;
    @alias default_image url('/img/image1.jpg');
     
    .class1 { color:color1; }
    .class2 { background-image:default_image;background-color:co lor2; }
    This way we could change colors or images for a whole webpage by editing a reduced number of lines.

    Had you considered any of these ideas in the past? If so, why were they rejected?
    • if you have 2 elements, eg ol#a and span#b, you need to double your selectors:
      ol#a *:first-child a:hover + dd, span#b *:first-child a:hover + dd { ... }

      Why is there no 'grouping' of selectors such as:
      ol#a, span#b { *:first-child a:hover + dd { ... } }

      And of course, there are more possibilities to greatly improve the maintainability of CSS-files; being able to define variables, or inline-calculations (eg. border-width: @var - 0.5em;

      Have they not been included to keep CSS simple, or ... ?
    • You can achieve the same effect, albeit in a slightly different way.

      For example, rather than define a variable and use it in style declarations throughout the document, you simply define one property of multiple selectors at once.

      So rather than

      H1 {color: col1; other-styles-here}
      PRE {background-color: col1; other-styles-here}

      you would, instead, write

      H1, PRE {color: blah}
      H1 {other-styles-here}
      PRE {other-styles-here}

      Now, it's not quite as elegant since it would separate logically-related style groups by forcin
  • CSS Evolution! (Score:5, Interesting)

    by eieken (635333) on Tuesday June 20 2006, @12:55PM (#15570832) Homepage
    Is the wave of webpages designed completely in CSS what you intially intended when you came up with CSS? Do you see that changing? Is that good or bad?
  • by ars (79600) <assd2@dsgml . c om> on Tuesday June 20 2006, @01:05PM (#15570901) Homepage
    Why did you forget to include the ability horizontally align multiple items?

    It's the main thing that's missing from CSS. Was it too hard to implement or write syntax for?

    I'm thinking something like:

    horizontal-align-to: .

    eg: horizontal-align-to: #box middle top; Will align the top of this element to the middle of #box.

    The same for vertical align would be nice as well. For horizontal elements restrict it to elements within a parent (and allow ID's (or use class name) to be duplicated within different parents, to make repeating multiple rows easier). For vertical it must be set on a block level element.

    Alternate syntax:

    On the reference element: horizontal-align-to: #name_me position;
    On the to be aligned one: horizontal-align-from: #his_name position;

    So:
    horizontal-align-to: #rowman top;
    horizontal-align-from: #rowman middle;

    Will align the middle of the element, to the top of rowman.
    • by ars (79600) <assd2@dsgml . c om> on Tuesday June 20 2006, @01:08PM (#15570928) Homepage
      Replying to myself: I may have switched horizontal and vertical in my post. I can see it going either way, but probably switched makes more sense.

      Also the top middle bottom stuff, they should take an offset: eg: middle-10px; not sure of how to write that in good CSS sytax though. And baseline, and the rest of the aligners are legal as well.
  • About Microsoft... (Score:5, Interesting)

    by Chabil Ha' (875116) on Tuesday June 20 2006, @01:08PM (#15570921)
    With MS's next browser release (IE 7), you mentioned in other interviews that their decision to not supprt CSS2 was more a political decision than a mechanical one. Aside from their obvious desire to dominate the world, what politics do you think are in play that make them not want to conform to the standard, and what do you think would change that landscape so that they would have some initiative to fully support it?
  • equal column heights (Score:4, Interesting)

    by crush (19364) on Tuesday June 20 2006, @01:09PM (#15570931)
    Is the difficulty of producing a layout that consists of three or more columns of equal height justification for adding some new feature to the specification to make this easier?
  • New standards (Score:5, Interesting)

    by iamsure (66666) on Tuesday June 20 2006, @01:12PM (#15570942) Homepage
    In your work at Opera, you have clearly paved a path that includes going beyond the W3C standards. Whether it is WhatWG implementations, or new functionality specific to Opera (2dgame), you are pushing into new territory.

    Can you explain why W3C isn't sufficient, and why efforts at Opera to expand beyond the standards differ from Microsoft's embrace/extend model?
  • by infestedsenses (699259) on Tuesday June 20 2006, @01:16PM (#15570974) Homepage

    As a developer who works with CSS every day, I find one complication that continues to bother me in my daily work. Support for CSS has always been good on the horizontal scope, but vertical positioning has always been quite complicated. Alone the procedure to affix a footer to the bottom of a screen in dependance of the amount of content is unnecessarily difficult, spawning hackish solutions such as "footerStickAlt" [themaninblue.com]. Centering an object in the dead center of a page also requires strange procedures such as this one [wpdfd.com], which still aren't ideal (try making the viewport really small). The old table method provided much easier methods for this. What are your thoughts on this and do you see improvement following in future CSS revisions?

  • Does CSS suck? (Score:3, Interesting)

    by dattaway (3088) on Tuesday June 20 2006, @01:17PM (#15570979) Homepage
    A collection of pages of Why CSS:

    http://www.decloak.com/Dev/CSSTables/CSS_Tables_16 .aspx [decloak.com]

    "I pretty much want to kick whoever invented CSS in the nuts."
  • by lord_sarpedon (917201) on Tuesday June 20 2006, @01:23PM (#15571035)
    Do you think that CSS is often misused? It seems to me that it is rarely used to define presentation in media other than the screen. As for my ideal stylesheet language... 1) Why must the layout be so linear? It seems to me that it would make more sense to have it operate closer to Autodesk Inventor, if you have ever used it, such that you set up whatever constraints (equal, parallel, etc) you see fit and the agent displaying the content finds a suitable solution. As an example, the login div must be equal width as the sidebar div, the sidebar div is at the left of the screen, the navbar is at the top of the screen and above the sidebar, and the content div is below the navbar and to the right of the sidebar. If everything is in a box, it would make sense to use other boxes as a reference point, rather than the screen. Pixels and percentages are nice and all, but not altogether natural. And pixels, while tempting, often don't cater to different resolutions. 2) Why would a spec for something that needs to be pixel-precise not come with an example implementation? 3) Shouldn't you be able to affect the document tree in a small way? If you are truly separating content and presentation, then why must I change the content to get the effect I want? I do this with XML + XSL + CSS, but just being able to add a div or image here and there would be nice...
  • by DysenteryInTheRanks (902824) on Tuesday June 20 2006, @01:33PM (#15571116) Homepage
    I have mod privs but no one else is asking this question, at least not in a respectful manner, so here goes:

    I understand the impetus behind CSS, and think it has brought some nifty things to the Web, particularly in terms of integrating with the DOM and thus helping usher in all the AJAXy goodness we're seeing lately.

    But CSS also seems to have spawned an anti-HTML jihad movement of people who rail against simple but effective HTML markup, including for example the B, I and FONT tags and the TABLE. Many people seem to make the principle of separating presentation from content a religious issue.

    I learned HTML in 1994 by using the View Source command in Mosaic and Netscape (beta). The simplicity of the tags made it very easy. I could keep the basic structure of a doc in my head: "<html><head><title>Home Page</title></head><body><p>Hello, <b>world</b>!</body></html>"

    For all the strenghts of CSS+XHTML, they are significantly more complicated to learn than basic HTML.

    Do you worry that CSS is scaring off new Web writers, espeically since basic HTML is increasingly deprecated among Web developers?
  • HTML5 (Score:3, Interesting)

    by booch (4157) <slashdot2009.craigbuchek@com> on Tuesday June 20 2006, @01:37PM (#15571159) Homepage
    Do you think HTML 5 (from the WHAT WG) will have a better chance of being accepted by the browser vendors than XHTML 2.0 or whatever else comes from the W3C? (I suppose being accepted by the dominant IE would be the most important.) As a more general question, how can we best create new standards that allow backward and forward compatibility? It seems that current browsers handle current HTML versions as special cases, by looking at the HTML version string. It seems that this would break the ability for these browsers to treat HTML 5 as if it were HTML 4.
  • {Gack.} (Score:5, Interesting)

    by Rob T Firefly (844560) on Tuesday June 20 2006, @01:43PM (#15571212) Homepage Journal
    Why the curly brackets? Those things get on my damn nerves.
  • Acid2 test? (Score:3, Insightful)

    by bigpat (158134) on Tuesday June 20 2006, @01:47PM (#15571250) Homepage
    Do you think the so called Acid2 test is a useful test for determing browser compliance with standards and if so then why? If it isn't a good test then is there a simple alternate test that could be more useful for browser developers?

    For your reference: http://www.webstandards.org/files/acid2/test.html [webstandards.org]

  • by BlueStraggler (765543) on Tuesday June 20 2006, @02:07PM (#15571403)
    Should it be possible to freely mix inline and block elements? In particular, place block elements inside inline elements? Basic HTML says no. CSS2 is vague, especially considering that an element's block/inline property is variable. Most browsers seem to side with HTML. But, coming from the TeX world, where \hbox and \vbox can be freely mixed to achieve any layout you like, I can see no compelling reason for prohibiting it. HTML/CSS can come across as hopelessly broken when you know that something analogous has been done for ages, and practically perfectly, elsewhere. Is the problem here with CSS, HTML, the browsers, or me?
  • Definition of pixel (Score:5, Interesting)

    by Sara Chan (138144) on Tuesday June 20 2006, @02:35PM (#15571617)

    The word pixel meant "picture element", but CSS redefined it to mean something quite different (a particular subtended angle of view [w3.org]). This causes confusion: CSS pixels are not pixels. (Indeed, I have seen misinformed comments on Slashdot due to that confusion.)

    My question is this: why call the subtended angle a "pixel", instead of something else (e.g. "subangle")? If CSS wanted to use the subtended angle for something, that is fine, but calling it a pixel seems to follow the approach of Humpty Dumpty—"When I use a word, it means just what I choose it to mean".

  • by oneiros27 (46144) on Tuesday June 20 2006, @03:11PM (#15571889) Homepage

    Why isn't there any easy way to style a table column in CSS?

    If you're serving legitimate, tabular data, and you want to right-align column #3 (normal for numerical data), you either have to apply a class to each cell, use javascript to apply it after the fact, or use hacks like:

    #tableid td+td+td { text-align: right } /* right align col 3 */
    #tableid td+td+td+td { text-align: inherit } /* stop right align at col 4 */

    Which work, but are difficult to maintain when you get 10+ columns, and don't try to automatically re-arrange columns with javascript.

    Why can't we just place styles on a <col> or <colgroup>, and have it cascade down?

    • Oops, messed up the formatting -- trying again:

      1. What would you most like to change with CSS? That is, if you could go back in time and change one thing in the spec and have it reflected today, what would be the most important thing?

      2. If you were allowed (perhaps by court order, which wouldn't be unthinkable) to force Microsoft to do one (1) change in Internet Explorer, what would that be?

      As a bonus question: What do you think of Slashdot's CSS? ;)