Last modified: 2014-04-15 01:03:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T61089, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59089 - VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection
VisualEditor: Changing the selected content's formatting (heading/paragraph/p...
Status: RESOLVED INVALID
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Trevor Parscal
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-28 21:29 UTC by Rummana Yasmeen
Modified: 2014-04-15 01:03 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Selecting the whole line (108.24 KB, image/png)
2013-12-28 21:29 UTC, Rummana Yasmeen
Details
Selecting multiple lines (86.03 KB, image/png)
2013-12-28 21:29 UTC, Rummana Yasmeen
Details
Observed Result (16.96 KB, image/png)
2013-12-28 21:30 UTC, Rummana Yasmeen
Details

Description Rummana Yasmeen 2013-12-28 21:29:01 UTC
Created attachment 14182 [details]
Selecting the whole line

Steps to reproduce:

1.Open a page with VE
2.Select a text to apply the paragraph format "Preformatted".Select the text in a way so that it selects the whole line.Check the screenshot of selection to better understand.

3.Now select the option preformatted from paragraph styling options

Observed Result:
The Preformatted option gets applied to the other following text/element even though they are not selected.

If the selection is done such way that it spans multiple empty lines then the preformatted options gets applied to those empty lines too.

See the screenshots attached.

Test Environment: http://en.wikipedia.beta.wmflabs.org/
Browser: Chrome Version 26.0.1410.65 
OS: MAC OS X 10. 8. 5 
Page:http://en.wikipedia.beta.wmflabs.org/wiki/28th_december
Comment 1 Rummana Yasmeen 2013-12-28 21:29:52 UTC
Created attachment 14183 [details]
Selecting multiple lines
Comment 2 Rummana Yasmeen 2013-12-28 21:30:32 UTC
Created attachment 14184 [details]
Observed Result
Comment 3 James Forrester 2014-01-18 05:27:02 UTC
Yes, content formatting applies to the line(s) selected, not the text selection. This is by design (rather than splitting the text). Closing as WONTFIX, but happy to discuss if someone things we should split instead.
Comment 4 Rummana Yasmeen 2014-01-21 20:00:16 UTC
Sorry, I think I could not explain it properly in my steps.The issue was not about applying the format on the whole line rather on an immediate following line which was not selected.

For example the content of a page is as follows:

The text
another text



Not selected text


Now if you select "the text" and "another text" but stop the selection just above the line "Not Selected text" and apply the format, it gets applied to "Not Selected text"

So, I am reopening the bug again as it is a different issue.
Comment 5 Trevor Parscal 2014-02-07 21:59:43 UTC
The selection of the following line is different than selecting the text on the line. If you choose to select just the text, you will get the behavior you are looking for. If you select the line and it's break (or empty lines after it) then you will get the behavior you are reporting as a bug.

This is not a bug, it's doing exactly what it should. However, it may be valuable to revisit how we can better communicate what is selected and how to achieve the desired result to the user.

Unfortunately, we have limited control over selection because we use ContentEditable, which is provided by the browser. The selection of a line and it's break may be something we can disable, but likely there will be negative effects on user experience and browser compatibility.

Marking as invalid, since this is not a bug, but a known feature. I'm happy to discuss the UX impact of this feature and possible changes that could improve the situation on a different, enhancement, bug.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links