Bug 227437 - can not properly edit text in input text boxes (pango disabled)
can not properly edit text in input text boxes (pango disabled)
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: epiphany (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-05 16:59 EST by Nikos Charonitakis
Modified: 2008-08-02 19:40 EDT (History)
0 users

See Also:
Fixed In Version: f8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-12-10 17:45:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nikos Charonitakis 2007-02-05 16:59:05 EST
Description of problem:i cant edit text in input text boxes. If i make a mistake
and have to move cursor back (using mouse or arrow keys) the cursor can be moved
only to the start or the end of a line or word...


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Matěj Cepl 2007-02-05 18:18:14 EST
Could be related to bug 227276?
Comment 2 Matěj Cepl 2007-12-10 04:24:17 EST
Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.

Setting status to NEEDINFO, and awaiting information from the reporter.

[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]
Comment 3 Nikos Charonitakis 2007-12-10 15:40:29 EST
this problem was fixed (if i remember right) after an upgrade.

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