Bug 94073 - ASSERT inSameLine(temp, prev) in VisiblePosition::previous() when clicking in wrapped text
Summary: ASSERT inSameLine(temp, prev) in VisiblePosition::previous() when clicking in...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-15 00:03 PDT by Shinya Kawanaka
Modified: 2014-09-05 06:51 PDT (History)
2 users (show)

See Also:


Attachments
Repro (680 bytes, text/html)
2012-08-15 00:03 PDT, Shinya Kawanaka
no flags Details
Repro2 (350 bytes, text/html)
2014-09-05 06:51 PDT, Renata Hodovan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shinya Kawanaka 2012-08-15 00:03:35 PDT
Created attachment 158511 [details]
Repro

When the element width is so small and the text in such element was rendered one character by one character, clicking somewhere right on that element will trigger an assertion.
Comment 1 Shinya Kawanaka 2012-08-15 00:04:21 PDT
Please resize your browser so that "something" is rendered like
s
o
m
e
t
h
i
n
g
Comment 2 Alexey Proskuryakov 2012-08-15 16:05:35 PDT
ASSERTION FAILED: inSameLine(temp, prev)
/Volumes/Data/Safari/OpenSource/Source/WebCore/editing/VisiblePosition.cpp(97) : WebCore::VisiblePosition WebCore::VisiblePosition::previous(WebCore::EditingBoundaryCrossingRule) const
1   0x10a4e0d9c WebCore::VisiblePosition::previous(WebCore::EditingBoundaryCrossingRule) const
2   0x10a4e0001 WebCore::VisiblePosition::characterBefore() const
3   0x10a4da08a WebCore::previousBoundary(WebCore::VisiblePosition const&, unsigned int (*)(unsigned short const*, unsigned int, unsigned int, WebCore::BoundarySearchContextAvailability, bool&))
4   0x10a4d9eba WebCore::startOfWord(WebCore::VisiblePosition const&, WebCore::EWordSide)
5   0x1092b9d17 WebCore::Editor::respondToChangedSelection(WebCore::VisibleSelection const&, unsigned int)
Comment 3 Renata Hodovan 2014-09-05 06:51:24 PDT
Created attachment 237687 [details]
Repro2

The previous test case doesn't trigger the assertion fail (for me) anymore. However, the second one fails on the same point.