CSS-2 Quick Reference Talk

  • Why not split this up into sections, [[CSS-2 Quick Reference:Box Model:Foo]] for example, and have information on "how" each implementation is Buggy/Partial/Supported, along with links to testcases you used to determine this at [[CSS-2 Quick Reference:Testcase_#]]?? [The way the page is currently, is a bit overbearing. And does not provide meaningful information on "what is supported/how". - Callek 00:41, 12 Jun 2005 (PDT)
  • You are definetly right, at the moment I am not sure how to organize this page, in fact it is linked only from my personal page. In my opinion this page should remain a Quick Reference. New page(s) has to be created to explicitly explain different browsers behaviours and relevant test-cases. Other comments and ideas are welcome. Lombardp 01:55, 12 Jun 2005 (PDT)
  • My thought is, that even without the "Supported"/"Not" stuff, the page is overbearing, you can supply a list of properties/selectors on that page, with links to specifics, and hell if you really want, supply a very brief spiel on them all, on the main reference page, just all syntax related stuff, can be best described on individual pages (and thus keep clutter out of here). As an aside, is it worth noting when an official CSS2[.1] property/selector is opened up with -moz- though not fully supported, etc.? - Callek 11:04, 12 Jun 2005 (PDT)
  • Ok, I'll try to summarize, just to see if I have understood:
    • You suggest to split the single page in multiple pages, one per section, and enrich each section with more details on browser-specific support and possibly a test-case. Then, provide a quick reference as a list of properties, without other info. I think this is the better solution.
      • Sounds exactly what I was suggesting. -Callek 08:30, 13 Jun 2005 (PDT)
    • For what regards the -moz- properties, I have been told that those properties are someway "temporary" and could be changed or removed at any time, more than one CSS expert told me not to use those properties in non-experimental websites, in order not to have compatibility issue in the near future. What do we do? Lombardp 23:58, 12 Jun 2005 (PDT)
      • Sounds perfectly legit, and yes, -moz- properties may be completely removed at any time. I was just not entirely sure the overal target audience here, and it seems that your target is web developers, which is entirely fine with me. -Callek 08:30, 13 Jun 2005 (PDT)