page 1 of 1
Comments: 3 | Views: 1703
#Jan 17th, 2008 @ 3:08 AM
RichardRudek
RichardRudek
So what do you expect for nothin'... :P
I'm trying to make a small contents table for a recent blog entry, but live.spaces keeps deleting the name attributes.

eg
<a href="#jumphere">Go There</a>
...
<a name="jumphere"></a>Whatever...

The underlined bit above gets deleted out of the html after it's published. WTF.  Is this not the way it's done anymore  ?
 
#Jan 17th, 2008 @ 3:38 AM
JChung2006
JChung2006
Try <a id="jumphere"></a> instead. See the HTML 4.01 specification for more details of what changed.
#Jan 17th, 2008 @ 4:15 AM
W3bbo
W3bbo
The Master of Baiters
RichardRudek wrote:
I'm trying to make a small contents table for a recent blog entry, but live.spaces keeps deleting the name attributes.

eg
<a href="#jumphere">Go There</a>
...
<a name="jumphere"></a>Whatever...

The underlined bit above gets deleted out of the html after it's published. WTF.  Is this not the way it's done anymore  ?
 


The WL Writer removes all non-XHTML attributes (yay!).

The way you're doing it is how it used to be done in the mid-90s, times have changed considerably Wink

"Named Anchors" are dead, consigned to the W3C's dumpster. The new hotness are Fragment Identifiers.

So whilst the means of targeting them remains the same: <a href="#fragment">, the way you define them is different. "fragment" just needs to be the ID of the element you're targeting.

Example:

<a href="#important">Jump to the important bits</a>

<p>[blah]</p>

<h3 id="important">Important Bits</h3>

<p>Important: at all times you must *****TCP CONNECTION DROPPED*****


This way, "#important" refers to the appropriately id'd header element "important".
#Jan 17th, 2008 @ 4:32 AM
RichardRudek
RichardRudek
So what do you expect for nothin'... :P
JChung2006 wrote:
Try <a id="jumphere"></a> instead. See the HTML 4.01 specification for more details of what changed.

I was reading from that spec, and I did try using id instead of name.
Same deal - it strips out the 'offending' attributes, leaving empty 'a' tags:
<a></a>

But I haven't tried webbo's suggestion, and probably won't. I've decided to make them separate posts, but posted in reverse order, so they appear one after the other.

The main reason for doing that is that there appears to be some 'rewriting' going on as it passes through the web pipeline, such that a link that starts out as ...cns!8B65F3DE0BE797AA!276.entry becomes something like ...27-05... or rather, the other way round.

Thanks guys.
page 1 of 1
Comments: 3 | Views: 1703
Microsoft Communities