Robust Client-Side JavaScript
molily.de
Robust Client-Side JavaScript
1–10 of 12 posts
Re: Robust Client-Side JavaScript
#2I got a 502 trying to visit, I suppose having robust JS doesn't mean much if your backend is not robust! lol
Re: Robust Client-Side JavaScript
#3It'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.
Re: Robust Client-Side JavaScript
#4It'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.
> 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 `
`, so you might try getting a browser with a better text reflow engine, or tweaking options on your current one.
Re: Robust Client-Side JavaScript
#5It'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.
> 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 ` `, so you might try getting a browser with a better text reflow engine, or tweaking options on your current one.
The site has the following rule in their CSS:
html { overflow-wrap: break-word; }
Re: Robust Client-Side JavaScript
#6Earlier quoted context omitted.
> 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 ` `, so you might try getting a browser with a better text reflow engine, or tweaking options on your current one.
The site has the following rule in their CSS: html { overflow-wrap: break-word; } which could be causing this at certain screen-sizes.
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.
Re: Robust Client-Side JavaScript
#7It'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.
> 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 ` `, so you might try getting a browser with a better text reflow engine, or tweaking options on your current one.
The page is styled to
overflow-wrap: break-word;
Re: Robust Client-Side JavaScript
#8Earlier quoted context omitted.
> 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 ` `, so you might try getting a browser with a better text reflow engine, or tweaking options on your current one.
The page is styled to overflow-wrap: break-word; But it's not clear what's triggering it
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.
Re: Robust Client-Side JavaScript
#9This is great material. Bookmarked!
Re: Robust Client-Side JavaScript
#10this can come in handy, nice!