Tested 6-14-09 Win32 build. After I launched Apprunner to create the profile, I put the following line under "user_pref("nglayout.compatibility.mode", 1); "in the prefs50.js file. user_pref("nglayout.widget.mode", 2); Then, I lanched Apprunner again to effect my change. At this time, "Scheduling later attempt to set content window" error displays several times. Apprunner will lanch, but Browser does not show anything.
Priority: P3 → P2
QA Contact: paulmac → teruko
Summary: Changing Prefs50 file to handle Widget mode causes Browser blank → Changing Prefs50 file to handle Widget mode causes Browser blank
Target Milestone: M7
This is not a prefs bug, it looks like a widget set bug.
not for m7, sorry marking m8 when gfx rendered widget will be official.
Can this be fixed sooner than M8? I18N functionality cannot be tested without the GFX text widgets. E.g., submitting i18n text/textarea for forms, or entering i18n data for email subjects. I could use this pref in the 6/8 build -- but at that time buster had not enabled text/textareas, so it only affected the other form widgets.
According to Kat Momoi, even though the browser window is hung, he can open up the messenger windows and he can type Japanese into the header fields.
Yes, I can see Japanese input in mail headers text field, but this option also disables any input in the mail body window. (The symptom is the same as described in Bug 8124 which had been fixed. But with this option on, the problem described there comes back.) Also it is not very stable. It crashes when I try to send mail.
As announced on the news groups, gfx rendered widgets are not ready for any real testing yet. Please do not submit any bugs on gfx-rendered widgets until they are officially turned on in M8.
Status: NEW → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 8410 ***
Moving all Widget Set bugs, past and present, to new HTML Form Controls component per request from karnaze. Widget Set component will be retired shortly.
You need to log in before you can comment on or make changes to this bug.