...that the official UCP wiki's source edit has the same layout as the legacy one, only the User Interface that were changed.
...that the official UCP wiki's source edit has the same layout as the legacy one, only the User Interface that were changed.
It's MediaWiki. The source code is still the same.
Yes, I just thought that the layout are still the same as the old one, but they only updated the UI
It's an update to the core software. It has new features and a new editor, but the source markup never changed. Though that's not entirely true; a couple of tags work differently now.
At the risk of sounding arrogant, the only way in which that is funny is if you didn't know how wikis worked.
I know how wikis work, but it is somewhat ironic...
...but if it works better that way, I'm fine with that
According to the screenshot, you are talking about the basic editor which is now used for CSS and JS, not even the 2010 editor. Indeed the simple editor, the 2010 editor, and the legacy source editor are basically just HTML text area with toolbars around. However, the 2017 editor is completely new thing that works very differently.
Actually, the 2010/code editor seems closer to the 2017 editor than the classic editor in terms of the HTML. Or maybe that is just because I use classic editor with syntax highlighting turned off?
Similar by what means?
I checked them now, and well the 2017 editor is not as heavily relying on JS as I thought (I expected something like the Feeds editor). However it uses <div contenteditable="true"> container and <p> childs to hold the code, and each character you type changes the DOM. The classic editor and the 2010 editor use a <textarea> element. Also the toolbars of the 2017 editor use fixed/sticky/JS-dynamic positioning (part of what mess it up on mobile) and the focus is always jumping for me, which is a bug but probably related to heavily involved JS too.
I can check again but that isn't what I think saw with the 2010 editor.
What do you think?