https://bugzilla.wikimedia.org/show_bug.cgi?id=65883
--- Comment #5 from Philippe Verdy <[email protected]> --- So the current Tech News needs correction. The expressions "block image" is ambiguous, at first reading I wondered who was right. Yes having client-side image resizing with just the addition of support of custom CSS for images would be a bonus. I know this works because this is already visible and used on the Mobile view even if it works with "max-width:100%" (used with the "box-model" quirk that should have never been used in its specific stylesheet, and which is absolutely not needed) It also works best with the support of "image sets" (now enabled by default in MediaWiki that can lists several thumbnail sizes, at resolutions 1x, 1.5x and 2x; but it could also add 0.5x and 0.75x for best results, letting browsers select the best interpolations depending on screen resolution and/or zoom mode; and ideally, the image sets for SVG images could also list the native SVG format for the best quality needed for images replacing complex text) ---- For now the current Tech News for this week (referencing this bug) needs fixing as it is interpreted as meaning all images. And what you call a "block image" is in MediaWiki an [[image:]] or [[file:]] with "left" or "right" floating-mode attribute, or "center", or "thumb(nail)" (your terminology is strange, because in HTML images are always inline by default, and even MediaWiki keeps them inline by placing the generated <img> element, possibly surrounded by an <a> element, within a block element). ---- Also, what is happening to image maps in the VisualEditor ? (they are also inline by default, and probably should be resizable by the client) -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
