Explicitly place '/' before fragment for multipage spec links

This prevents us from 301 redirecting, which could cause the fragment to
get lost
This commit is contained in:
Corey Farwell 2015-10-10 12:07:10 -04:00
parent 85f2b6fc5b
commit 9b68d715de
97 changed files with 152 additions and 152 deletions

View file

@ -78,16 +78,16 @@ fn collect_text(element: &Element, value: &mut DOMString) {
}
impl HTMLOptionElementMethods for HTMLOptionElement {
// https://html.spec.whatwg.org/multipage#dom-option-disabled
// https://html.spec.whatwg.org/multipage/#dom-option-disabled
make_bool_getter!(Disabled);
// https://html.spec.whatwg.org/multipage#dom-option-disabled
// https://html.spec.whatwg.org/multipage/#dom-option-disabled
fn SetDisabled(&self, disabled: bool) {
let elem = ElementCast::from_ref(self);
elem.set_bool_attribute(&atom!("disabled"), disabled)
}
// https://html.spec.whatwg.org/multipage#dom-option-text
// https://html.spec.whatwg.org/multipage/#dom-option-text
fn Text(&self) -> DOMString {
let element = ElementCast::from_ref(self);
let mut content = String::new();
@ -95,7 +95,7 @@ impl HTMLOptionElementMethods for HTMLOptionElement {
str_join(split_html_space_chars(&content), " ")
}
// https://html.spec.whatwg.org/multipage#dom-option-text
// https://html.spec.whatwg.org/multipage/#dom-option-text
fn SetText(&self, value: DOMString) {
let node = NodeCast::from_ref(self);
node.SetTextContent(Some(value))