add links
mdn: markdn worked nicely years ago, now, if mdn is unstranslated, leads to page not found. i prefer to leave full English path, easier for translators (me) to check & change
@joaquinelio I guess we should ditch mdn://, replace it everywhere with long links to MDN?
Not pretty

well... "GOOD NEWS!" The user gets the link. Not that enthusiastic news.
Yes.
-
I cant do an easy replace mdn: ---> http... With Full path, I can check just from the editor or github site
-
Not that bad if you leave Eng

-
The best: Once inside MDN, with the previous scroll youll leave your frustration to MDN.
Sooo, should I replace every mdn: with long ones?
- The best: Once inside MDN, with the previous scroll youll leave your frustration to MDN.
What's the 3rd variant? ;)
ping @joaquinelio
sorry... grammar again and the mad old man I'm growing inside me was just kidding they weren't variants, they were the enumeration of advantages full path gives when
no MDN transl is available
- !!!!!!!!!!!!!!!
MDN: User is frustrated because
javascript.infoleads to 404.
FULL: User is frustrated becauseMDNdoesn't show his/her language.
so, don't take me always too seriously. Still useful anyway.
Guess, the only clean way is to replace mdn: with full urls.