It's a game that's in closed beta. I should be able to get a key for someone who needs to test this. I also have it, so you could use my machine to run some tests. The basic STR are: 1. Go to http://alliances.commandandconquer.com/en/ 2. Log in (if not already logged in) Expected result: See "My Games", then a header thingy, then "Closed Beta 2", going down the page. Actual result: the header thingy is invisible, although you can still click on it. The bug also affects buttons and dialogs in the game: instead of having the desired background, they have a mostly transparent (and thus pretty hard to use) background. This was regressed by bug 497995, specifically: changeset: 83265:dda1146d1ec3 user: William Chen <wchen@mozilla.com> date: Thu Dec 22 18:34:45 2011 -0500 summary: Bug 497995: Part 1 - Implement border-image revisions in latest css3-background spec. r=dbaron It looks like bug 713643 might be for some related issues.

The relevant bits of CSS from the website would be useful here.

According to the DOM inspector, the element in question is (URL removed): <div style="-moz-border-image: url("blah.png") 6 6 6 6 / 1 1 1 1 / 0 0 0 0 stretch stretch; position: absolute; line-height: 0; font-size: 0px; overflow: hidden; -moz-box-sizing: border-box; border-width: 6px; top: 0px; left: 0px; pointer-events: none; width: 399px; height: 36px; z-index: 5;"></div>

They need a border-style of some sort now. This is a TE bug.

It would useful if somebody who got a key directly from them for the closed beta contact them. I bet they are listening to their beta testers.

David: why don't you act as a contact person, since you're a "beta tester"?

(In reply to Chris Lawson from comment #5) > David: why don't you act as a contact person, since you're a "beta tester"? Sure thing. I'm no expert on CSS, so could you please clarify for me what >They need a border-style of some sort now. means, and I'll communicate with the EA devs?

(In reply to David Mandelin from comment #6) > (In reply to Chris Lawson from comment #5) > > David: why don't you act as a contact person, since you're a "beta tester"? > > Sure thing. I'm no expert on CSS, so could you please clarify for me what > > >They need a border-style of some sort now. > > means, and I'll communicate with the EA devs? Basically, -moz-border-image implies border-style: solid. With the unprefixed version (which will probably ship in 13) it no longer implies that.

(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #7) > Basically, -moz-border-image implies border-style: solid. With the > unprefixed version (which will probably ship in 13) it no longer implies > that. Thanks. I passed that on to one of the devs.

(In reply to David Mandelin from comment #8) > (In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #7) > > Basically, -moz-border-image implies border-style: solid. With the > > unprefixed version (which will probably ship in 13) it no longer implies > > that. > > Thanks. I passed that on to one of the devs. David - Do you know if the devs got back to you on this? Was this problem fixed? This happens to be a tier 1 app for the mozilla marketplace, so if we need to get traction on this, let me know.

This bug has existed since version 15 (funny, since I was running 15.0A1 nightly when I signed up and couldn't figure out what was going on with the game, I assumed it was the game, not the browser...) 14, 13 and 12 have all worked well with this game for me. Which means when 15 does get released, all of us FF players will be screwed, as I can't think of anyone who doesn't use Firefox and Greasemonkey for some nice game addons. From my eye, it just seems that some of the textures aren't being downloaded and/or used. On a very slow connection, 13 looked a lot like 15 shows until everything gets downloaded from the server. I had that experience a couple weeks ago while I was on vacation. :S I never noticed an issue with game mechanics though. And I'm replying because an alliance mate running 15 Beta has found he can't read what's written now.

This is a website bug. David, what was the result of your outreach efforts?

(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #11) > This is a website bug. > > David, what was the result of your outreach efforts? FYI - I also outreached via BD (Thomas Elin) to EA directly with a report of what to do to fix their site. Tom might be a good person to also ask about this.

Tracking so can try to avoid shipping this regression.

(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #11) > This is a website bug. > > David, what was the result of your outreach efforts? Someone at EA told me the bug was in the framework they use to build the site, not in their code, so they couldn't fix it directly. I think they said they could try to report a bug, or fix it, or something, but clearly nothing's happened yet. I'll ask again.

(In reply to David Mandelin [:dmandelin] from comment #14) > Someone at EA told me the bug was in the framework they use to build the > site, not in their code, so they couldn't fix it directly. I think they said > they could try to report a bug, or fix it, or something, but clearly > nothing's happened yet. I'll ask again. Can you ask what framework EA uses so that we can work to get the framework updated?

We use qooxdoo - rolled out to revision 1.4 in production which still have the issue. But they already did some changes to the framework a while ago with https://github.com/qooxdoo/qooxdoo/commit/d64a808153c79434c9c09ff3fe0dea3a67443a45 which means that the issue no longer exists in our products - we upgraded to revision 2.0.1 which got the fix in, already. It should be out on production servers during the next 2-3 weeks.

We're shipping FF15 on August 28th - will your framework be updated by then? Does bug 778137 still exist once updated?

The current 15.0 beta renders the game properly. I believe this bug can be closed.