Closed Bug 16886 Opened 20 years ago Closed 20 years ago
[PP]Input field contains character symbol by default
Build: Apprunner Version: 1999102008 Platforms: Mac Other Platform: Works on Windows 95, Linux (Red Hat 6.0). Expected Results: The input field show be empty by default What I got: A "cross" symbol is displayed in the input field. Steps to reproduce: 1) Launch Apprunner 2) Open test cases: http://slip/projects/marvin/html/input_size.html 3) The input field contains the symbol.
Reassigning to Kevin.
reassigning to buster
assigned to brade, since it's a mac-only bug. kathy, can you see what's going on here? all the code involved on the content and layout side is XP, the only platform code involved here is rendering (I think.) cc'ing the other editor macheads in case anybody knows anything about this. Chris, do you see this in all text controls, or just this one simple test case?
This looks fine to me in a build from yesterday.
Oh, I do see this now, even in the editor init page. It looks like we're getting one char extra from somewhere.
Oh, these symbols are showing up elsewhere too. See the mail start page for an example. I think someone in layout left in some debug code.
Aha! these are non-breaking spaces showing up. See the editor init page for examples.
Kipp owned up to causing this. Reassigning.
This sounds like an encoding problem to me.
(charset MacRoman vs. Latin1)
*** Bug 16889 has been marked as a duplicate of this bug. ***
*** Bug 16878 has been marked as a duplicate of this bug. ***
*** Bug 16986 has been marked as a duplicate of this bug. ***
I still see this bug on Mac. It no longer appears in the editor window but it does appear in each empty input textfield. Reopening bug.
Can you please debug it out then on the mac? I don't see it on linux...thanks
reassign back to Kipp. I think he now has enough info to debug this himself.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → FIXED
With kathy's help, it's fixed.
Fixed in the Nov 1 build (1999110108).
You need to log in before you can comment on or make changes to this bug.