Nope, tried that earlier. I should add that this occurs when squishing the window so that the width of the map is smaller than the space to the left of the infobox, causing it to wrap to under the infobox. Seems to always do it for me, even on a different computer that hasn't ever accessed the wiki.
Also, sorry User:Arawn76 for hijacking your comment thread lmao.
Ah, okay, didn't have the right width before. It only happens in a certain range and the layout is okay again when the image is larger than the main page space or something like this …
@CompleCCity, pls reread it, i said i see it critical to pull to much out of the assets, next come textures?! That's an ironic comment. No offense, nothing. I have my experience, my opinion. You use raw maps on the infomap. What shall this bring? That's an original file, ok, but without layers. One very good made map with all infos says more out. And if someone wanna see the raw map it's on a global page like defiance bay or endless path better placed. Tool topic is the same, use as less as necessary, so you never have to think about it. Because you use allready different styles one on the world map another one in twin elms, then that map tool on other pages. The tool can be avoided. @Macklin am used to it. Glad no one said "Hands up, this a robbery".
Given that this is literally my job as a wiki manager, some clarifications:
1. Including the original background layers is not copyright infringement, not any more than including transcriptions of books, dialogues, ending slides, walkthroughs, items, etc. We do it under Fair Use doctrine for educational/informational purposes. It has no discernible impact on the sales of the game(s), to boot.
2. Extension:Imagemap is part of the stock MediaWiki configuration and is not from another source. The link refers to a GUI that I use to make imagemaps, which is not proprietary. The problem with the imagemap popping over/under the text when the infobox appears is an issue with how MediaWiki displays elements on the page, not anything from a third party site (since, again, Imagemap is part of our MediaWiki loadout.
3. Remaking every page to match Elms' Reach is going to take a while. Feel free to do it, but that's going to be very time- and resource-intensive. I speak from experience.
Finally, on a personal note, I repeat my earlier point: Forcing users to click through to the file page and then manually type in the target location they read off the image is just bad user experience.
Hey man, I fixed Hearthsong, you accidentally cut out a good chunk of the article. :)
Nope, tried that earlier. I should add that this occurs when squishing the window so that the width of the map is smaller than the space to the left of the infobox, causing it to wrap to under the infobox. Seems to always do it for me, even on a different computer that hasn't ever accessed the wiki.
Also, sorry User:Arawn76 for hijacking your comment thread lmao.
Ah, okay, didn't have the right width before. It only happens in a certain range and the layout is okay again when the image is larger than the main page space or something like this …
@CompleCCity, pls reread it, i said i see it critical to pull to much out of the assets, next come textures?! That's an ironic comment. No offense, nothing. I have my experience, my opinion. You use raw maps on the infomap. What shall this bring? That's an original file, ok, but without layers. One very good made map with all infos says more out. And if someone wanna see the raw map it's on a global page like defiance bay or endless path better placed. Tool topic is the same, use as less as necessary, so you never have to think about it. Because you use allready different styles one on the world map another one in twin elms, then that map tool on other pages. The tool can be avoided. @Macklin am used to it. Glad no one said "Hands up, this a robbery".
Oh and thx for the link i've bookmarked it.
Given that this is literally my job as a wiki manager, some clarifications:
1. Including the original background layers is not copyright infringement, not any more than including transcriptions of books, dialogues, ending slides, walkthroughs, items, etc. We do it under Fair Use doctrine for educational/informational purposes. It has no discernible impact on the sales of the game(s), to boot.
2. Extension:Imagemap is part of the stock MediaWiki configuration and is not from another source. The link refers to a GUI that I use to make imagemaps, which is not proprietary. The problem with the imagemap popping over/under the text when the infobox appears is an issue with how MediaWiki displays elements on the page, not anything from a third party site (since, again, Imagemap is part of our MediaWiki loadout.
3. Remaking every page to match Elms' Reach is going to take a while. Feel free to do it, but that's going to be very time- and resource-intensive. I speak from experience.
Finally, on a personal note, I repeat my earlier point: Forcing users to click through to the file page and then manually type in the target location they read off the image is just bad user experience.