actions buttons for Modal not visitable(but can click) on Chrome 16.0.912.41 beta

[iron9light]

• Mint linux 11 64bit
• Chrome 16.0.912.41 beta
• jquery 1.7.1
• bootstrap 1.4.0
• bootstrap-modal.js 1.4.0

It's no problem on firefox 8.0

            <form method="post" action="#">
                <fieldset>
                    <legend>Your API Key</legend>
                    <div class="clearfix">
                        <label for="api_key">API key</label>

                        <div class="input">
                            <input class="xlarge" name="api_key" type="text" value="12345678910111213141516171819"
                                   readonly="readonly"/>
                            <a class="btn primary" data-controls-modal="resetWarning" data-keyboard="true">Reset</a>
                        </div>
                    </div>
                </fieldset>
                <div class="modal hide fade" id="resetWarning">
                    <div class="modal-header">
                        <a href="#" class="close">&times;</a>

                        <h3>Warning</h3>
                    </div>
                    <div class="modal-body">
                        <p>Will you reset your API key?</p>
                    </div>
                    <div class="modal-footer">
                        <a class="btn primary" id="resetButton">Reset</a> <a class="btn secondary" id="cancelButton">Cancel</a>
                    </div>
                </div>
            </form>

and

$(function() {
  var closeModal, resetKey;
  closeModal = function() {
    return $("#resetWarning").modal("hide");
  };
  resetKey = function() {
    $("input[name=api_key]").val("abcdefghijklmnopqrstuvwxyz");
    return closeModal();
  };
  $(".modal #cancelButton").on("click", closeModal);
  return $(".modal #resetButton").on("click", resetKey);
});

http://twitter.github.com/bootstrap/ and demo in http://twitter.github.com/bootstrap/javascript.html work fine.

[iron9light]

I've tried jquery 1.7.0, same as 1.7.1
and 1.6.4, worse. Nothing happens when clicked the buttons.

[imbstack]

From what I could find, buttons and form elements are not visible.

It seems that hotlinking the css as in

<link rel="stylesheet" href="http://twitter.github.com/bootstrap/1.4.0/bootstrap.min.css">

makes the modal dialog work properly in all browsers that I tested, but using it with less breaks the modal in chromium.

[futhr]

Using the rails gem and have the same issue on OSX, Google Chrome 15.0.874.121 (latest). Tried different combinations using "a" "button" tags. Its there -but not visible. Funny, it works better on IE8 then on Chrome which has many other issues with the modal but will not comment them here.

[jdejong]

I can confirm 1.4 using the .fade class on the modal dialog non-text elements (form, a, button etc...) are not displayed. Issue appears to be in the following css:

-webkit-transform-style: preserve-3d;

When I remove it using Chrome Dev Tools all the missing elements are shown. It appears to be a stacking issue because all the elements are in there correct location as the OP noted.

[fat]

preserve-3d was removed almost immediately after the release - this should be working if you use the latest stable 1.*

[prognostikos]

I can confirm that even without preserve-3d I still see the problem on Chrome 16.0.912.63 beta on OS X when the fade class is applied.

Removing .fade fixes the bug.

Using twitter-bootstrap-rails gem version 1.4.2.

[fat]

1.4.3 is the latest. Also, you would need both fade and in.

[andrexx]

Interesting. Where I can find information about new releases 1.4.x ? In all sources only used 1.4.0 version. Or just use latest changes from master?

[fat]

you should definitely use the latest from master, but i don't what i was talking about yesterday.

[sekati]

I think the confusion on whether this works or not is due to the fact that the git tag for 1.4.0 (Date comment: Thu Nov 3) is actually a different/older build than that served up by http://twitter.github.com/bootstrap/1.4.0/bootstrap.css - which is more recent (Date comment: Sat Nov 12) - even though they have the same version number.

To make matters worse the later (non git tag'd version) is the one that works, the tagged version contains the bug.

It would be useful to make a 1.4.1 git tag for those of us still using 1.4.x & running up against this bug (the difference is, as mentioned the newer build omits -webkit-transform-style: preserve-3d whereas the tagged version does not).

[sekati]

@fat Can we re-open this issue since the bug still exists in the tagged version (just not the hosted one)?