If you've been looking for a way to get a custom scroll bar onto your web page, without worrying about all the clunk of browser compatibility, you might want to check out the FleXcroll Customizable, Standards Compliant ScrollBar by Hesido.
This is what the author, Hesido, had to say about the features of their scrollbar: "fleXcroll supports mouse-wheel and keyboard scroll (from version 1.5.0), and text selection aid (from version 1.7.5) so people can text-select overflowed contents, making it behave almost the same as (and in some cases better
Cleaning the code in the edited content is one important new addition in KTML 4. You have the option to choose from cleaning only the Word tags, only the CSS formatting, or cleaning all the formatting tags inside the code. Saving the code as XHTML compliant is also one of KTML's possibilities.
To make this completely possible, you must however install and configure the HTML Tidy utility:
1.
Download and install the HTML Tidy version suited for your particular server configuration. You need a version released in 2005 or higher.
2.
If you are
Creating Valid HTML Documents Means Cleaner Code and Easier Maintenance
I'll be the first one to let you in on a secret: building Web pages isn't hard. With the software that is available now, you can write your Web page and have it up and viewable in half an hour. And with these tools, why would you need to run an HTML validator on your HTML to find errors? Well, you don't have to, but if you want your pages to stay viewable through future versions of HTML, or you want newer browsers to be able to display it correctly, then writing valid HTML is the
Why bother with keeping your code up to date with what the W3C recommends? Don't! Please, put up bleeding-edge Web pages that take advantage of bugs in browsers. Contribute to the working anarchy we fondly call the Internet.
While I do not enjoy stylistic exploits that unknowingly (or even knowingly) create security holes, exploits that contribute to the art world -- even if they only last until everybody updates their browser to the next version -- are wonderful.
Pushing the boundaries of design is part of the Zen experience of the Web. However,
Document types have been a part of HTML for a long time, but few developers use them even though they are required in order to be compliant. XHTML is no different, and an additional XML tag can, and usually should, be used. Section 3.1.1 "Strictly Conforming Documents", of the XHTML 1.0 specification describes this in detail, so read the chapter for a complete overview.
Usually, your document type declaration will look something like this:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Thus far, you've read the HTML 4.01 and XHTML 1.0 documentation and you understand their relationship. You have successfully converted a few documents to XHTML 1.0. So, how do you know that your documents are really XHTML 1.0 compliant?
The easiest way, as stated earlier, is to use "xmllint." It was distributed with later versions of libxml, which can be obtained from xmlsoft.org. Once properly installed, you can use xmllint to check your work. Your command line entry will look like this:
xmllint --valid --noout mydoc.html
If you receive error
Why bother with keeping your code up to date with what the W3C recommends? Don't! Please, put up bleeding-edge Web pages that take advantage of bugs in browsers. Contribute to the working anarchy we fondly call the Internet.
While I do not enjoy stylistic exploits that unknowingly (or even knowingly) create security holes, exploits that contribute to the art world -- even if they only last until everybody updates their browser to the next version -- are wonderful.
Pushing the boundaries of design is part of the Zen experience of the Web. However,
Thus far, you've read the HTML 4.01 and XHTML 1.0 documentation and you understand their relationship. You have successfully converted a few documents to XHTML 1.0. So, how do you know that your documents are really XHTML 1.0 compliant?
The easiest way, as stated earlier, is to use "xmllint." It was distributed with later versions of libxml, which can be obtained from xmlsoft.org. Once properly installed, you can use xmllint to check your work. Your command line entry will look like this:
xmllint --valid --noout mydoc.html
If you receive error
RSS/XML