|
Posted by cwdjrxyz on 07/28/07 22:13
On Jul 28, 1:57 pm, Paul Furman <pa...@-edgehill.net> wrote:
> I know it's wrong but it works: putting the <title> in the body of the
> document inside another <head> because I'm generating this with php &
> kind of boxed myself into not having access to the text I want till I
> get well into the body, for example:http://edgehill.net/gallery/photo-update/6-24-07/pg1pc1
> I noticed that duplicate titles have no effect.
>
> --------------
> Also, regarding length, the W3C folks sayhttp://www.w3.org/Provider/Style/TITLE.html
> "Whilst there is no limit on the length of a title (as it may be
> automatically generated from other data), information providers are
> warned that it may be truncated if long."
>
> I have no problem with truncating, the alternative would be for me to
> truncate it myself. I'm gathering the titles from photo annotations
> which are sometimes a long paragraph of text like:http://edgehill.net/gallery/cameras/pg1pc3
>
> Mozilla strips this to a about 300 characters:
> 1) Gitzo G1298 tripod with Linhoff LN9051 ball head 2) TC-14E AF-S
> teleconverter 3) TC-20EII AF-S teleconverter 4) Tokina 300mm f/2.8 MF
> (most of that is lens shade & teleconverters 5) MC-20 release 6) 105mm
> f/2.8 AF-S VR Micro 7) Nikon D200 8) 135mm f/2
>
> IE7 strips it to about 100 characters:
> 1) Gitzo G1298 tripod with Linhoff LN9051 ball head 2) TC-14E AF-S
> teleconverter 3) TC-20EII AF
>
> --
> Paul Furman Photographyhttp://edgehill.net
> Bay Natives Nurseryhttp://www.baynatives.com
The W3C shows many validation errors, but your page works on 5 common
browsers I have to test. If you end your url with just pg1, pc1, or
just a slash, you get 3 different pages, one being a photo of a bay
area country view. Likewise, using the error <script language =
javascript 1.2> instead of the now required <script ="text/
javascript"> works, despite being an error. The same for several other
errors. The point is that all or some browsers may work for certain
errors. However, with the next version upgrade, the browser may not
work with some errors that it did before. Then the webmaster may have
to hack a way around the problem or correct errors to get a certain
browser to work again. Of course some new browsers have bugs,
especially IE ones, but these usually are detected fairly early and
posts in groups such as this point out the problem and how to get
around it.
Navigation:
[Reply to this message]
|