I'd suggest using an attribute over a type specifier too. Not only does it have the problem Marius spotted, but if you specified a type attribute then you have much more difficulty displaying content of the same type from both a CDN and dynamic user content in the same page (such as in a social networking site, displaying user-uploaded images from one location and the static images for the site layout from a CDN).<br>
<br>Other than that, I think this would be a good addition that would make <base> much more usable in dynamic sites.<br><br><div class="gmail_quote">2009/11/9 Marius Gundersen <span dir="ltr"><<a href="mailto:gundersen@gmail.com">gundersen@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">One problem with the first proposal is that you don't know the mimetype of the content before you load it. Just because it ends in .gif does not mean it is a gif file (eg, using GD a .php file could be a GIF image). <br>
<br>Instead of using class, maybe the rel attribute would fit better. <br><font color="#888888"><br>Marius Gundersen</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Mon, Nov 9, 2009 at 8:43 PM, Fabian Freiburg <span dir="ltr"><<a href="mailto:f.freiburg@googlemail.com" target="_blank">f.freiburg@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Dear list!<br>
<br>
DISCLAIMER<br>
I've never used a list before and I've never posted a proposal, so please be patient with me if I'm doing something wrong.<br>
<br>
PROPOSAL<br>
The "base" element is very helpful. Trouble is that it affects all
relative links and "src" attributes. Especially for the "src"
attributes it would be very useful if it could define a context or
media type to which it belongs. With this it would be possible to
define a "base" URI fore. g. images, javascripts or stylesheets.
Furthermore it would be very easy to use a CDN for serving static media
files. There are probably some more advantages.<br>
<br>
There are different ways to implement this feature: One idea is to use
a "content" or "type" attribute, where the MIME type to which the
"base" belongs can be defined. For example the following "base" would
affect all GIF images:<br>
<base href="<a href="http://example.com/media/images/" target="_blank">http://example.com/media/images/</a>" type="image/gif"><br>
<br>
Another idea is to use some kind of tagging, which would mean more flexibility. For example:<br>
<base href="<a href="http://example.com/media/images/" target="_blank">http://example.com/media/images/</a>" class="images cdn gif"><br>
Each element using one of the classes will belong to the relevant "base" element.<br>
<br>
Please let me know what you think about it.<br>
<br>
Regards,<br><font color="#888888">
Fabian<br>
<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>