Robust Client-Side JavaScript

dmartinez 8 years ago |

Does anyone know of guides that are similar in style/scope to this that apply to server-side development?

lerie82 8 years ago |

I like the part where the p's and q's overlap the underline. and also, it's a nice guide I have saved to PDF

purplecones 8 years ago |

This is great material. Bookmarked!

jaequery 8 years ago |

this can come in handy, nice!

send_computers 8 years ago |

I got a 502 trying to visit, I suppose having robust JS doesn't mean much if your backend is not robust! lol

tempodox 8 years ago |

It's good to have a comprehensive document like this.

The document itself could be made more readable by choosing to break lines at word boundaries, not in the middle of words.

Vendan 8 years ago | |

> The document itself could be made more readable by choosing to break lines at word boundaries, not in the middle of words.

What browser are you using? I see none of this happening, and looking at the source code, it's just blocks of text in `<p>`, so you might try getting a browser with a better text reflow engine, or tweaking options on your current one.

lucideer 8 years ago | | |

The site has the following rule in their CSS:

    html { overflow-wrap: break-word; }

which could be causing this at certain screen-sizes.

Vendan 8 years ago | | |

only if the word is too long to fit on a line by itself. If the browser is breaking it at the end of a line instead of flowing it to the start of the next line, then it's in violation of the spec.

33degrees 8 years ago | | |

The page is styled to

    overflow-wrap: break-word;

But it's not clear what's triggering it

Vendan 8 years ago | | |

which, by spec, only allows breaking the word if the word is too long to fit on a line by itself. You'd need like a 1 inch wide screen to hit that edge case from what I've been testing.