README.txt
author Masayuki Nakano <masayuki@d-toybox.com>
Fri, 29 Jul 2016 13:29:45 +0900
changeset 394879 43eb79cff14baebb79ef8bc02df57b544d876534
parent 289120 ae64d16898395607093db2e2dd667b6544cb1f55
child 306729 29617b97dd36cecdfcb11340f8ea2e7c3c729b68
child 313991 53c9d4821a559e9ecdd38726af0f6c6d8107082e
child 326860 99b39cd9daa267fae6cd95a0192b1cd1e093d29a
child 348761 c5e638d867ae17cf212438c52db8dd73fc0be1e6
child 389835 5243745d0b77604f6105e07ab2edb0593def9257
child 394059 d04b5a591b84ef80cddd4446e80ff14814dbd51e
child 428217 293fca44fda4e7cc0970f71b12024a14a40267b4
child 433150 d6ca56a87cf1456bb2a786546788b03a78a70d94
child 454032 564b17f6d9323f3e2dfb7a550735681af2021ede
child 491484 2e0e6bcef472c68a6feec06c57096ea9af608313
child 496966 ba37a2701a763962b01f7f7fe178fca16ab6cecd
child 501891 146751ba88f6dde8972b83ed262bae517fa2459e
permissions -rw-r--r--
Bug 1286464 part.17 ContentEventHandler::OnQueryTextRect() should compute a line breaker's rect from the last text frame if the queried range starts with a block frame r?smaug When queried range starts with a block frame, we cannot compute proper line breaker's rect at its open tag only with the frame's rect because the proper rect should be at the end of previous text frame. Therefore, this patch makes SetRangeFromFlatTextOffset() return the last text node found at scanning the range. Then, OnQueryTextRect() can compute the first line breaker's rect with it (if there is at least one text node). However, if the last text node is hidden by CSS or something, this patch won't work. We need to do something in another bug for hidden frame's issue, though. But note that IME typically doesn't request hidden text's rect because neither selection nor composition string is in such range. MozReview-Commit-ID: 2FFzNoubJ1y

An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:

    https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure

For information on how to build Mozilla from the source code, see:

    http://developer.mozilla.org/en/docs/Build_Documentation

To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:

    http://developer.mozilla.org/en/docs/Creating_a_patch
    http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree

If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]

You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:

    https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
            - or -
    http://nightly.mozilla.org/