Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6762995
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T14:25:28+00:00 2026-05-26T14:25:28+00:00

Just updated jQuery UI from 1.8.5 to 1.8.16, and the modal dialogs I’ve been

  • 0

Just updated jQuery UI from 1.8.5 to 1.8.16, and the modal dialogs I’ve been using succesfully in my app stopped showing all of a sudden, by which I mean that the overlay is displayed correctly, but the actual box is not showing at all.

Dialog creation and usage is straight forward:

var dlg=$('<div></div>').dialog({modal:true,autoOpen:false});
dlg.html('some content');
dlg.dialog('open');

This used to work fine. Now I just get the overlay, no actual dialog box.

Required JS is loaded fine (single jQuery UI file, containing all dependencies, plus the jQuery lib), also the CSS (using Smoothness theme), checked with Firebug.

There are no errors or warnings in the Firebug console.

The only change I made to the downloaded distribution was rename some of the files by removing the version number and “ui”, i.e. jquery-ui-xyz.js becomes jqueryui.js. As I said, the scripts load fine.

I have seen the few questions here regarding the same problem, but no real answer. Before rolling back or start altering my previously working code, please let me know if I’m missing something here.

Many thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T14:25:28+00:00Added an answer on May 26, 2026 at 2:25 pm

    Solved. One of those stupid cases where the apparent problem is just a red herring, and the real problem lies somewhere else.

    What I did was, altered a single variable in my MVC framework, which caused the jQuery UI scripts and other essential scripts to load in the head section, instead of the body section. I did this just before upgrading jQuery, and did not test the effect, assuming nothing would change: what, I just moved the scripts around, I’ll get an error if something goes wrong, I’ll catch it then.

    Thing is, one of those scripts contains the above code. And it’s now loaded in head. I have to assume that creating a div element via JS in the head section of a document is not gonna work, is it? And that’s a silent fail, no error issued!

    I then upgraded jQuery, and got the above described problem. I got mislead further by the lack of any error report, and the fact that the usual culprits (not properly loading scripts and CSS) were not to blame here.

    I pulled my hair out since, until I got it tonight and solved it. I deserve that for not making incremental changes to the project, testing at each step, esp. before such a significant sub-framewok overhaul.

    So, apologies to the jQuery team. My bad.

    TL;DR: It wasn’t jQuery’s fault. It was bad developing practices all along. Also, make sure you don’t create a jQuery UI Dialog object in the head section of your page (however stupid that sounds).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I just updated an app from .NET 2.0 to .NET 4.0 and I have
I just updated jQuery from 1.6.2 to 1.6.3 and find out that inline edit
I just updated from jQuery 1.3.2 to 1.4.3, and I'm seeing some new behavior
I have a website that's using jquery.ie6hover.js (https://github.com/gilmoreorless/jquery-ie6hover) And I've just updated to latest
I just updated my OS from Snow Leopard to LION 10.7.3, and I usually
I have just updated my site to use a jQuery plugin jquery.raty.min.js The plugin
I have just created a new MVC 3 project and updated all the installed
I was just wondering how I can animate the jQuery form ui's div update
I just updated virtualbox to the latest 4.1.16 r78094 and realized that I can
I just updated PHP 5.2.0 to 5.2.11 and now I am getting loads of

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.