Closed Bug 195770 Opened 23 years ago Closed 19 years ago

{inc}Submission form inside table wiggles (moves) making it hard to click on submit button

Categories

(Core :: Layout: Tables, defect, P3)

x86
All
defect

Tracking

()

RESOLVED FIXED
Future

People

(Reporter: vanbalen, Unassigned)

References

()

Details

(Keywords: testcase)

Attachments

(2 files, 2 obsolete files)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030301 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030301 2003030105/Linux-trunk Whenever I try to click on "Show my bikes" on the page below, the form (which is inside a table, AFAICT) wriggles out from under my mouse pointer and I have to be very quick in order to click it... it's almost like the web developer that made that page made some kind of sick joke, except that I doubt that's the case. http://www.giant-bicycles.com/us/030.000.000/030.000.099.asp?answerid=8757 The html on the page seems kind of messy and appears to include some overlapping tables, which might be a problem. However, I don't know enough about what's valid in html to diagnose myself. Reproducible: Always Steps to Reproduce: 1. Go to listed http://www.giant-bicycles.com/us/030.000.000/030.000.099.asp?answerid=8757 and try to clik on "Show my bikes" 2. Notice that it's very hard to click on button with form wiggling around. Actual Results: Form wiggles and writhes to keep from being submitted. Expected Results: Form should be good and cooperative and let me submit it with minimal ado.
Attached file testcase —
testcase exhibits the problem with linux trunk 20030302 originally, all 4 "foobar"s are on one line. after clicking the button, all 4 "foobar"s are on separate lines after mouseup, there are 2 "foobar"s on each of two lines.
this seems to actually be a tables bug ==> layout/tables
Assignee: form → table
Component: Layout: Form Controls → Layout: Tables
Keywords: testcase
QA Contact: desale → madhur
This sounds like 183756 to me. *** This bug has been marked as a duplicate of 183756 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Nope. That bug is definitely specific to positioning.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Summary: Submission form inside table wiggles making it hard to click on submit button → {inc}Submission form inside table wiggles making it hard to click on submit button
Sorry, my bad.
http://www.mozilla.org/search.html and clicking the submit button exhibits a similar behaviour.
Priority: -- → P3
Target Milestone: --- → Future
seeing bug on testcase, so marking OS: ALL Mozilla Trunk BuildID 2003091704 on Win98 Replacing Original URL, as it doesn´t show the bug, new URL shows it clearly. Don´t fill anything in, just click 'Search' ;-) New URL is: http://www.mozilla.org/search.html Original URL was: http://www.giant-bicycles.com/us/030.000.000/030.000.099.asp?answerid=8757 doesn´t show the bug, but if I select 'Men's Frame', on submitting I get: Microsoft OLE DB Provider for SQL Server error '80040e14' Line 1: Incorrect syntax near 's'. /general/dbase.asp, line 330
*** Bug 207922 has been marked as a duplicate of this bug. ***
Added (moves) to summary. Users wanting to report this bug aren't likely to search for "wiggles".
Summary: {inc}Submission form inside table wiggles making it hard to click on submit button → {inc}Submission form inside table wiggles (moves) making it hard to click on submit button
I have a cleaned up example of this behavior. Will attach buttonRelocate.html. I've discovered that removing either width: 50% from the table's style or leaving the cell font size to the default corrects things. Hope this is helpful. Testing on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007.
See my 2003-11-20 12pm EST comment below.
Depends on: 147558
Attached patch patch (obsolete) — — Splinter Review
For the testcase, the ReflowChild at nsTableRowFrame::IR_Target gets cellMet.mMaximumWidth from the width of the submit button, however the mMaximumWidth of the cellFrame has right value. I think that the value should be exchanged.
> I think that the value should be exchanged. I think that the value should not be exchanged.
Component: Layout: Tables → Accessibility APIs
Component: Accessibility APIs → Layout: Tables
If the block code returns a a wrong cellMet.mMaximumWidth why should the cell overwrite it? Shouldn't that fixed be in the block code.
Attached patch patch (obsolete) — — Splinter Review
With the following code and flow, if the table has percent width and the cell's colspan is larger than one, the prefWidth is not right value. nsTableFrame::BalanceColumnWidths(...) { ... mTableLayoutStrategy->BalanceColumnWidths(aReflowState); ... CalcMinAndPreferredWidths(aReflowState, PR_FALSE, minWidth, prefWidth); ... } nsTableFrame::BalanceColumnWidths | +-->BasicTableLayoutStrategy::BalanceColumnWidths | | | +-->BasicTableLayoutStrategy::AssignPctColumnWidths | | | | | +-->BasicTableLayoutStrategy::ComputeNonPctColspanWidths | | | | | +-->colFrame->SetWidth(DES_ADJ, WIDTH_NOT_SET); | | (colFrame->mWidth[DES_ADJ] is set to -1) | +-->mTableFrame->SetPreferredWidth(perAdjTableWidth); | (perAdjTableWidth is right preferred width) +-->nsTableFrame::CalcMinAndPreferredWidths | +-->width = colFrame->GetDesWidth(); (width is not right value)
Attachment #165873 - Attachment is obsolete: true
Can you please attach a reflow log and a analysis what goes wrong there? I suspect stronlgy that we get a wrong cellMet.mMaximumWidth from the block code. I know the structure of table reflow so these diagrams lead to nowhere.
Comment on attachment 166573 [details] [diff] [review] patch Sorry, I do not know how to run a reflow log. My posted patch (attachment 167743 [details] [diff] [review]) to Bug 103582 includes the fix of this problem.
Attachment #166573 - Attachment is obsolete: true
I moved and updated the docs for it today http://www.mozilla.org/newlayout/doc/frame_reflow_debug.html. If you have problems with the steps in Getting the log just contact me.
Depends on: 103582
I see no change to the layout of "Cleaned up example of behaviour" with both: - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/2006120606 Minefield/3.0a (pre-reflow branch) - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/2006120804 Minefield/3.0a1 (post-reflow branch) However, with the original testcase, with - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/2006120606 Minefield/3.0a (pre-reflow branch) I click the button and the layout changes With: - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/2006120804 Minefield/3.0a1 (post-reflow branch) I click the button and the layout does not change.
Indeed. The cleaned up testcase was apparently a different bug. Resolving fixed-by-reflow-branch
Status: REOPENED → RESOLVED
Closed: 23 years ago → 19 years ago
Depends on: reflow-refactor
Resolution: --- → FIXED
Flags: in-testsuite?
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: