Closed
Bug 1168005
Opened 9 years ago
Closed 9 years ago
[e10s] NS_QUERY_TEXT_RECT to content process doesn't return mString
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla41
People
(Reporter: m_kato, Assigned: m_kato)
References
Details
Attachments
(1 file, 1 obsolete file)
1.36 KB,
patch
|
masayuki
:
review+
|
Details | Diff | Splinter Review |
It requires on Cocoa's implementation.
Assignee | ||
Updated•9 years ago
|
tracking-e10s:
--- → ?
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → m_kato
Assignee | ||
Comment 1•9 years ago
|
||
Assignee | ||
Comment 2•9 years ago
|
||
Comment on attachment 8610008 [details] [diff] [review] NS_QUERY_TEXT_RECT should set mString I forget this :-<. NS_QUERY_TEXT_RECT should set mString. It is used on Cocoa's widget.
Attachment #8610008 -
Flags: review?(masayuki)
Assignee | ||
Comment 3•9 years ago
|
||
Comment on attachment 8610008 [details] [diff] [review] NS_QUERY_TEXT_RECT should set mString Oops, this is invalid patch
Attachment #8610008 -
Flags: review?(masayuki)
Assignee | ||
Updated•9 years ago
|
Attachment #8610008 -
Attachment is obsolete: true
Assignee | ||
Comment 4•9 years ago
|
||
Assignee | ||
Comment 5•9 years ago
|
||
Comment on attachment 8610012 [details] [diff] [review] NS_QUERY_TEXT_RECT should set mString Cocoa widget uses mString parameter by NS_QUERY_TEXT_RECT. But it isn't implemented on e10s yet.
Attachment #8610012 -
Flags: review?(masayuki)
Comment on attachment 8610012 [details] [diff] [review] NS_QUERY_TEXT_RECT should set mString >+ (mIMECacheText.Length() > aEvent.mInput.mOffset + >+ aEvent.mInput.mLength) ? >+ aEvent.mInput.mLength : UINT32_MAX); nit: (mIMECacheText.Length() > aEvent.mInput.mOffset + aEvent.mInput.mLength) ? aEvent.mInput.mLength : UINT32_MAX; Looks nicer to me. But I guess, you implement EndOffset() to the mInput is smarter. And also, shouldn't be |>=| ?
Attachment #8610012 -
Flags: review?(masayuki) → review+
Assignee | ||
Comment 7•9 years ago
|
||
(In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) (working slowly due to bad health condition) from comment #6) > And also, shouldn't be |>=| ? greater than or equal is better rather than original. but if equal condition, it is same result (
Updated•9 years ago
|
https://hg.mozilla.org/mozilla-central/rev/102b30c582cd
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•