Last modified: 2014-06-11 06:31:08 UTC
There is a difference in behavior between explicitly stating "none" in the image wikitext and setting no alignment (which is usually default) This difference is especially complicated when we're dealing with switching between block to inline, as inline images basic/frameless have no initial alignment (attrs.align = undefined) but if an alignment is chosen in basic/frameless they turn into blocks. There is no real way to choose "none" alignment for inline blocks with our current GUI. You can see the outcome and differences between default/no alignment to 'none' and other alignments in each of the different image types in this table: https://www.mediawiki.org/wiki/User:Mooeypoo/VE_ImageAlignment I've tried to explore what other programs do in this case, but there doesn't seem to be a good analogy for the difference between having 'float' value and not having a float value while mixing block with inline. In Microsoft Word 2013, images are inserted as block image with default alignment that is the direction of the text (left for ltr, right for rtl) *BUT* without text wrapping - so no float. You can change the image to inline ("In Line with Text") or to be wrapped ("With Text Wrapping") but the wrapping options are limited to how close the text is around the image; the user is then allowed to manually drag the image wherever they want ti to be (no actual 'left' / 'center' / 'right') We should find a working solution to let users decide between having 'none' alignment explicitly while still having the default value available for both inline and block images.
Created attachment 15623 [details] Word 2013 image alignment menu
Created attachment 15624 [details] Word 2013 image popup menu
Created attachment 15625 [details] Word 2013 image position menu
Created attachment 15626 [details] Word 2013 image wrap text menu
Created attachment 15627 [details] Image alignment in Google Docs
Interestingly enough, in Google Docs you seem to have three main alignment options: * In line - an inline image * Wrap text - Block image with floating, you can then drag/drop it either left, center or right in the text and choose how small the margin to the text is. * Break text - this is just like our "none" option, it's an image in its own line that is automatically aligned to the text (so, left in LTR) The functionality (drag/drog) and some options aren't all relevant, but maybe we could get some ideas from the naming of the features.
(In reply to Moriel Schottlender from comment #6) > Interestingly enough, in Google Docs you seem to have three main alignment > options: > > * In line - an inline image > * Wrap text - Block image with floating, you can then drag/drop it either > left, center or right in the text and choose how small the margin to the > text is. > * Break text - this is just like our "none" option, it's an image in its own > line that is automatically aligned to the text (so, left in LTR) > > The functionality (drag/drog) and some options aren't all relevant, but > maybe we could get some ideas from the naming of the features. Dragging to the left/right/centre actually could be really nice, but we'd probably want both that and a way to set it in the dialog I think. "Inline" vs. "Break text" vs. "Wrap text" seems reasonable language…
The comparison to wikitext functionality should be something like: * In line: frameless/basic without alignment * Wrap text: thumb/frame/frameless/basic with explicit right/left alignment * Break line: thumb/frame/frameless/basic with either "center" or "none" alignments. No float, no text wrap. The only problem in that case would be to adjust the fine print of the behavior, but in general terms it would be more or less consistent to the user.
