Welcome Safari Users
4 Comments
Fixed a few bugs. Now Safari should have no problems.
The following is a list of all entries tagged with bugs.
The code is fairly simple: img:after { content: “Hello World”; }. It displays the text “Hello World” right after an image. It works in Opera, but not in Firefox! Why is that? Isn’t Firefox supposed to be the new black?
For those of you pondering the Why of this, try out img:after { content: “(” attr(alt) “)”; } for show. It’ll type out the contents of the ALT attribute after an image.
What would probably be considered a bugfix release, Wordpress 2.01 has been released.
Among the changes I’ve been looking forward to:
See the full bugfix list, and download the package.
A few days ago, I updated both my Noscope and Fauna weblogs from Wordpress 1.5.2 to Wordpress 2.0. The upgrade process was smooth and simple.
But it seems Wordpress 2.0 wasn’t quite ready for primetime, atleast for me. The problem, I’ve tracked down, is related to the way Wordpress now handles permalinks. It seems the implementation doesn’t work on my setup, which is to have my main blog in the /journal/ directory, and show only a digest on the frontpage. The result? /journal/ is now a badly designed 404 page, and conditional tags aren’t working.
How is Wordpress 2.0 working for you?
Use ultra simple CSS properties to make sure only one browser sees it: Internet Explorer.
Use conditional comments to show code to a specific Internet Explorer browser.
Use this fix if your DIVs “bleed” in Internet Explorer.
Are you experiencing a horisontal scrollbar that shouldn’t be there?