MODx 0.9.1 rev 609 (internal testing)

Quote from: sottwell at Dec 16, 2005, 02:30 PM

In your Adventures with FF 1.5 on OS X, did you by any chance check the template select in the document editing page in the manager?

On my end, none of the drop-downs appeared to work on a document editing page. But all work in the System Configuration section. Not sure why.

In other news, I’ve committed the menu changes to the trunk. One bug that seems unavoidable at the moment has to do with Opera. I’ve tried to fix the bug but Opera just doesn’t want to cooperate. Being as it appears that there is more than one issue with Opera and MODx, I’m considering this particular bug rather moot at the present. Until we get rid of the frames entirely, it’s going to be a little tricky to get the manager working right in Opera. Case point, you can’t resize the doc tree window in Opera for some reason. I haven’t really seen anyone on the forum complaining about Opera so...let it be for now!

Man I go onsite to a client for a day and miss all the fun! Great work folks... sounds like lots off good progress yesterday.

Here’s the latest/greates SVN export ... rev 609.

I tore apart the mutate_content.dynamic.action.php file, and narrowed it down to one section:

Lines 463 to 489 contain the code for the menu bar, including the Edit Document title, the Save,Delete and Cancel buttons, and the four radio buttons.

Something in that section of code is what is locking up the select dropdown. I’m still experimenting, on a line-by-line basis to try to completely isolate the problem, but it’s acting very strangely.

For example, just emptying the div container still has the dropdown failing, but removing or even changing the class name of the div and it works. That is very odd, because other pages, using the same div, such as the System Settings page, work just fine.

Go Susan Go!

Quote from: rthrash at Dec 17, 2005, 01:15 PM

Go Susan Go!

Yeah! Put a can of Raid on that $#!t!

That’s good news as far as that bug is concerned. Just the fact that you isolated it down to a particular section is very good to hear!

I just commited some more QE stuff. Mostly small changes and fixes but should get tested before we release.

I strongly suspect it’s an odd combination of things, involving the javascript and possibly the CSS. It’s happened before in other browsers. And the Mac version is getting a lot of flak over its problems.

Are there any ff nightly builds that address some of the problems?

I just tried their 1.6a.1 and it’s still doing it.