Skip to main content

Search and Top Navigation

#4626 closed bug (fixed)

Opened June 22, 2009 06:20PM UTC

Closed October 16, 2012 03:34PM UTC

Dialog: Broken layout when using animation

Reported by: kristiandamian Owned by:
Priority: major Milestone: 1.8.22
Component: ui.dialog Version: 1.7.2
Keywords: animation Cc:
Blocked by: Blocking:
Description

When i call a dialog window with the follow code, i got the dialog bad formed, but when i comment the "show" parameter i got my dialog perfect.

I attach the code (just the dialog call) and a couple of screenshots,

This error only appears in firefox 3.0.1, i also tried in chorme and IE7

Attachments (3)
  • badDialog.PNG (88.3 KB) - added by kristiandamian June 22, 2009 06:24PM UTC.

    the dialog with the bad display

  • code.js (0.4 KB) - added by kristiandamian June 22, 2009 06:21PM UTC.

    this is the code who create the dialog

  • welldialog.PNG (89.7 KB) - added by kristiandamian June 22, 2009 06:24PM UTC.

    the dialog ok

Change History (6)

Changed July 03, 2009 09:08PM UTC by scottgonzalez comment:1

milestone: TBD1.8

Changed November 12, 2009 03:31AM UTC by scottgonzalez comment:2

summary: error when display a dialog window in firefoxDialog: Broken layout when using animation

Changed May 23, 2011 11:24AM UTC by techtangents comment:3

http://jsbin.com/eheja3 has kristiandamian's code in it.

Works fine for me on:

  • Firefox 4.0.1 / Ubuntu 11.04
  • Chromium 11.0.696.68 (84545) / Ubuntu 11.04

Need to re-test with FF 3.0.1, per the original report.

Changed September 07, 2011 12:39PM UTC by scottgonzalez comment:4

keywords: → animation

Changed October 11, 2012 02:47PM UTC by scottgonzalez comment:5

milestone: 1.9.01.10.0

Changed October 16, 2012 03:34PM UTC by bchiasson comment:6

milestone: 1.10.01.8.22
resolution: → fixed
status: newclosed

I was unable to reproduce using the specific version of Firefox, however, the bug in the jsbin was present for the latest version of Chrome (22+). Changing to the latest version of jquery and updating to 1.8.22 resolved the issue.