Linux: Cannot get focus in file input textfield

VERIFIED FIXED in M18

Status

()

P1
normal
VERIFIED FIXED
19 years ago
18 years ago

People

(Reporter: mcafee, Assigned: blizzard)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta3+][nsbeta2-], URL)

Attachments

(2 attachments)

(Reporter)

Description

19 years ago
Linux.
Try and create a patch for bug 40698, by
typing in a pathname for a file into the patch location
text field (file picker widget).  you never get focus!
Note that using the browse... button seems to work.
(Reporter)

Comment 1

19 years ago
oh let's pick on this bug instead of another one,
URL now points at this bug.

Comment 2

19 years ago
related to bug 45749 perhaps?

Comment 3

19 years ago
Say, Chris, do you mean the HTML <input type="file"> in the attachment page
(which, yes, does not apparently get focus). When I saw this earlier I assumed
you meant pav's filepicker.

In a testcase, html onfocus and onblur event handlers seem to say that the focus
leaves the ender widget as soon as it arrives (but I could be reading that
wrong). [This is linux only; the testcase works on mac and win32]. Looks like an
mjudge/saari/pavlov thing

Comment 4

19 years ago
Created attachment 11555 [details]
testcase; simple <input type="file">
(Reporter)

Comment 5

19 years ago
this is needed for basic bugzilla usage, nominating
for nsbeta2.
Keywords: nsbeta2

Comment 6

19 years ago
Putting on [NEED INFO] radar. PDT needs to know impact to user.  Why is using 
browse not a sufficient way to pick a file?  The user can still type in the file 
into the field in the browse window right?
Whiteboard: [NEED INFO]
(Reporter)

Comment 7

19 years ago
user should be able to type full file path in.
browse... button is acceptable workaround, but !
who knows how many other things are broken.
(Reporter)

Comment 8

19 years ago
saari
Assignee: trudelle → saari
Component: XP Toolkit/Widgets → HTML Form Controls
(Reporter)

Comment 9

19 years ago
browse... button is acceptable workaround, but this is pretty broken
and a fix should be taken for nsbeta2+ if possible.
Making the summary more accurate, so that this doesn't sound like a filepicker
bug.
Summary: Linux: Cannot get focus in text part of file picker → Linux: Cannot get focus in file input textfield

Comment 11

19 years ago
This is broken, but with an obvious workaround.  Annoying, but it does not fit
the criteria we are using for triaging for nsbeta2. Must fix for release,
nominating for nsbeta3.
Keywords: nsbeta3
(Reporter)

Comment 12

19 years ago
reiterating, we should take a fix for this if there is one, for beta2.

Comment 13

19 years ago
This is obnoxiously broken... I'm looking at it now

Status: NEW → ASSIGNED
Priority: P3 → P1

Comment 14

19 years ago
Putting on [nsbeta2-] radar. Not critical to beta2. 
Whiteboard: [NEED INFO] → [nsbeta2-]

Comment 15

19 years ago
I'm seeing this, too.  I have to use middle-mouse-paste to attach anything to a
bug.

Comment 16

19 years ago
Adding nsbeta3+, assigning to bryner 
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3+]
Target Milestone: --- → M18
Really assigning to me.
Assignee: saari → bryner
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Checked in a fix.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 19

19 years ago
This should really go into the M17 branch as well.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Updated

19 years ago
Status: REOPENED → ASSIGNED
(Assignee)

Comment 20

19 years ago
Created attachment 12203 [details] [diff] [review]
patch that was checked in

Comment 21

19 years ago
re-nominating for nsbeta2; we have a fix in hand and it isn't very dangerous;
this will affect the useability of the beta for at least people in our
engineering groups. we even have non-netscape engineers ready to commit and test
the change.
Whiteboard: [nsbeta2-][nsbeta3+] → [nsbeta3+]
(Assignee)

Comment 22

19 years ago
reassign
Assignee: bryner → blizzard
Status: ASSIGNED → NEW
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 23

19 years ago
We cannot take risk for PR2 at this time.  Putting on [nsbeta2-] radar.  
Workaround is to use Browser button. Putting on relnote2 radar.
Keywords: relnote2
Whiteboard: [nsbeta3+] → [nsbeta3+][nsbeta2-]
(Assignee)

Comment 24

19 years ago
This is checked into the tip.  No need to keep it open.  I'll just patch the
RPMS I distribute of M17.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 25

19 years ago
Closing
Status: RESOLVED → CLOSED
Reopening so I can set this to RESOLVED, so it will show up on QA's radar.
Status: CLOSED → REOPENED
Resolution: FIXED → ---
This is checked in.
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago19 years ago
Resolution: --- → FIXED

Comment 28

18 years ago
Verifying on Build 2000-09-18-06-M18
Platform:
  -Red Hat 6.2
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.