Link to home
Start Free TrialLog in
Avatar of mathprof
mathprof

asked on

why does input button move?

Using VBSCript,
I have 3 input buttons which I want to appear next to each other on the same row across.

Using FrontPage 2000, in NORMAL MODE they show up next to each other as I want them. In Preview mode, however, the are one under another (in a column). When I click on the first button, in preview mode, they now line up next to each other on one row across.

If I click on the 2nd or third buttons, they stay in a row across.

Now, I change the values of the 2nd and third buttons and the web page shows the new values. However, when I click on the THIRD button, the are now one UNDER the other in a column.

Any ideas?
Avatar of mathprof
mathprof

ASKER

Here's the code that I'm using to create the 3 buttons:

<P id=buttons STYLE= "visibility:hidden; position:absolute; top:250; left:175">
<input type="button"  value="Get A Problem" name="RANDOM" >
  <input type="button" value="<< Previous Step" name="BACK"><font color="#FFFFFF">
  <input type="button" value="Next Step>>" name="FORWARD"></font>
<BR><BR>
</P>

This sounds like a question for th HTML/ASP topic area, but I'll take a crack at it:

I've found that different browsers react differently to buttons.  Some browsers force all buttons to be the same size; others size the buttons according to the text displayed on them.

Given this, when your browser is set to a certain width, the buttons will often wrap to the next line since they don't fit on the current line.

One way to overcome this problem is to drop them into different cells within a table (3-cells wide: 33% each or the expected size of the button.)
ASKER CERTIFIED SOLUTION
Avatar of aminerd
aminerd

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,
Your code worked nicely. Thanks for the quick reply.
Prof Weissman
Darn!  My message came in after mathprof posted the code, so I never saw it or I would have had time to submit that code!  Good job, aminerd.
Hi rspahitz,
I'm sorry about the points, but aminerd's code solved my problem.
Prof Weissman