User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.18) Gecko/20081031 SeaMonkey/1.1.13 Build Identifier: In SeaMonkey 1.1.14 the password input field is not displayed at https://www.wellsfargo.com - running Win32 with no extensions. This works properly with previous versions. Reproducible: Always

This may be the same as bug 387971 which was closed as "works for me". This is the relevant line of HTML line for the password field: <span class="mozcloak"><input type="password" accesskey="P" id="password" name="password" size="13" maxlength="14" style="float:left;width:147px;" tabindex="2" /></span> The Wells Fargo homepage uses the stylesheet at a248.e.akamai.net/f/248/1856/90m/www.wellsfargo.com/home.css which references mozcloak as follows: .mozcloak {-moz-binding: url("//a248.e.akamai.net/f/248/1856/90m/www.wellsfargo.com/IdentityMap.xbl#mozcloak");padding:0;margin:0} IdentityMap.xbl binding source: <?xml version="1.0"?> <bindings xmlns="http://www.mozilla.org/xbl" xmlns:html="http://www.w3.org/1999/xhtml"> <binding id="mozcloak"> <content> <html:span> <children/> </html:span> </content> </binding> </bindings>

Given the different domains of the main document and the binding, may be it is not SeaMonkey problem, but I leave this to the experts. The usage of -moz-binding in this case seems rather pointless to me. Here's a workaround for anyone needing it badly: either use View -> Use Style -> None, or add the following rule to the user style sheet (either userContent.css or using the Stylish extension): @-moz-document url(https://www.wellsfargo.com/) { .mozcloak { -moz-binding: none !important; } }

Error console message: Security Error: Content at https://www.wellsfargo.com/ may not load data from https://a248.e.akamai.net/f/248/1856/90m/www.wellsfargo.com/IdentityMap.xbl#mozcloak.

Re: comment #2 While Mozilla-specific CSS properties might be useful during development and testing of the Gecko core and might even be useful when developing new Web pages, this makes me question whether such properties should be used for Web pages targeted to the general public. Indeed, Mozilla-specific CSS properties could be considered dangerous and avoided just as proprietary Internet Explorer capabilities should be avoided. There is no public input or review of the specifications for these properties as there is for W3C specifications. I'm beginning to think the Product for this bug report should be changed to Tech Evangelism and that someone officially representing the Mozilla organization communicate with Wells Fargo as to why the latter's Web site should not be using Mozilla-specific CSS properties.

I changed the product to Core since it is a rendering issue and the original bug was for Core. I agree that Wells Fargo definitely should not be using Mozilla-specific CSS properties but something changed in Core (Gecko 1.8.1.19) which made this issue appear. Note this problem does not occur with SeaMonkey 1.1.13 (or earlier) or SeaMonkey 2.0 alpha 2.