My layout looks fine in firefox and internet explore, but in google chrome it looks bugged.
My Search is placed somewhere else.

Any idea why and what cause ths?

Dani AI

Generated

Browsers often disagree for predictable reasons: broken or missing markup (each engine repairs the DOM differently), subtle float/clear/containment rules, and differing default styles for form controls and inline elements. In this thread saw the search box move only in Chrome — that pattern usually means the problem is in HTML/CSS structure rather than a mysterious browser-only bug.

A practical debug checklist:

  • Validate the HTML and CSS (W3C validators) and confirm a standards DOCTYPE is present.
  • Reduce the page to the smallest test case that still shows the error; this isolates the cause.
  • Use Chrome DevTools (Elements / Computed) to inspect the search element and its parents: check computed width, margins, float status, and whether a parent has an established block formatting context.
  • Toggle properties live (float/position/display/overflow) to see what change restores layout.

Common, reliable fixes: make a float-containing parent establish a new block formatting context (for example by applying a clearfix or overflow:auto), set explicit widths or box-sizing to avoid padding/width differences, and normalize form-control styles across browsers. A modern clearfix:

.clearfix::after {
  content: "";
  display: table;
  clear: both;
}

Thanks to for pointing toward float/positioning as the likely area to check, and to for the reminder to include a minimal example — reduced test cases and screenshots are what let others reproduce and diagnose layout quirks quickly. ’s report that it’s fixed confirms that the issue was local to the page structure, not a Chrome rendering bug.

Recommended Answers

All 4 Replies

change float:left to float:right on line 197

commented: He asked for it. Ha ha ha. +6

I did not give out any code. a joke? haha... not really....

Member Avatar for Member #120589

I thought it was funny. If you don't want people to take the piss, post your code and include screenshots. Perhaps you'll get serious replies then.

Well, I'm asking what the cause of these bugs are in generally.
I've heard many say they have had problems with coding it for each browser.

Anyways, I fixed it.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.