amelierosalyn.com

Skip navigation

All posts tagged with "CSS"

Learning curve

I started out on the web back in 2000, using Geocities' Pagebuilder to make such awesome (read: terrible) things as this... thing. Speaking of Geocities... Anyone remember that lovely little popup window that used to come up while the Pagebuilder was loading? I used to have time to have lunch before it finally loaded. Oh, the joys of dial-up... Anyway, I then moved onto Microsoft Publisher (oh dear) and FrontPage (...yep) before I realised that I actually knew how to write HTML without the need for a WYSIWYG editor.

By 2003, I found I could make layouts, too. By "layouts" I mean the type of thing that was popular then - mostly stock images plastered with 87554376967 Photoshop brushes. I was particularly proud of this one (oh dear God...) and this one (a few years later, admittedly... I had discovered the joy of CSS by then!). I had even got them to work in both IE and Firefox! Go me!

The point of this is that now, in 2012, knowing CSS 2 and HTML 4/XHTML 1 is really not that great. We're looking at HTML 5, CSS 3, jQuery, responsive design and lots of things that weren't around when I first started all this, and having had a break of sorts from all this webby business for the past few years, I find myself very much behind the times. I feel a bit weird about having to essentially relearn what I knew, but at the same time I find myself frustrated that I'm not quite up to date with everything. The same goes for PHP and Ruby - I learned PHP back when PHP 4 was just out, and Ruby/Rails when it was still on version 1.8.5/Rails 1.2. I've been dipping in and out and getting up to scratch where I can, but I still think I've got a long way to go. Now to find the time to do all this learning...

IE7

So the first public IE7 beta has come out (source). Of course, I had to download and try it straight away.

...And guess what, I'm disappointed. Why? Because Microsoft haven't fixed half the bugs that IE6 had. I was reorganising this site's CSS earlier to get rid of IE hacks since IE7 doesn't like them (yes, that was the reason for the red text. Sorry if I blinded you) and these are the mistakes I found IE7 still to have:

  1. The float bug still exists.
  2. This bug exists too - when you quote a comment on this here site, the "Orginally posted by" text goes missing for some unknown reason. Could also be because of this, I'm not sure which it is.
  3. Some block-level elements still don't default to display: block; without specifying so in the CSS (and likewise for some inline elements)
  4. This bug has been slightly rectified but it still caused me a major headache because IE was refusing to "listen" to margins specified by #id element when #id > element was also specified - even when the former was written afterwards. In Firefox/Opera/Safari, it doesn't matter whether you write it as #id element or #id > element - if the former is written after the latter, it will override it (I think? I actually haven't tested it! >.< ).

There are more, but I can't be bothered to list them. In short, I had hoped the old peek-a-boo thing would be resolved but it hasn't been, neither have the weird floating problems or width/padding/margin bugs. Blah. Oh, and they (Microsoft) completely ripped off Firefox with their "new features". Tabbed browsing? Live bookmarks? Damn, IE, where have you been?!
/geeky subjects

And now I must go and install a new guestbook on a site I've done for someone because hey guess what, it's being spammed to death. The site's been up for 2 years and only in August did I allow it and my brother's site to be listed on search engines. Now look what happens, spam! Part of the reason why I think this site's been rather lucky in terms of comment/form spam is that it's not indexed by Google or any other major search engine. It's listed, but definitely not indexed (that I'm aware of). Any sub-domains are spammable since they don't have the robots.txt file in their root directories. I did try putting some in, but hostees kept deleting them thinking they were spam or something and anyway it didn't seem to work. The whole disallow / part seemed to make the bots think I meant / of my domain rather than the subdomain and indexed it anyway. So yes, I'm prepared to sacrifice search engine listings for having less spam. Grrrrr. Think I'll go for another installation of Jem's BellaBook. Hopefully blocking some common words should mean stupid porno spammers keep the hell out. Having said that though, they leave "genuine" messages with no specific keywords. Katy blogged about this a while ago - "normal" messages such as:

Hello admin! your site it is so great and useful! I have definitely bookmarked it and will come again! Great work!

...are too similar to genuine ones and are therefore almost impossible to block. ARGH.