(In reply to James Forrester from comment #22)
> (In reply to Bryce Glover from comment #21)
> > I'm still seeing this bug with Safari 6.1.4, guys; maybe it's more serious
> > than we all think?  It would be really nice if we could figure out what's
> > going on here, because it's really annoying for me to not be able to use
> > VisualEditor since it's such a great product (I can't even access the
> > 'Switch to Source Editing' command since the menus hide behind page content!)
> 
> Hey, sorry, please re-open bugs if you think more work needs to be done on
> them. This bug was lost to the mists of time (bugs marked RESOLVED/VERIFIED
> are only looked at by happenstance). :-(
> 
> Unfortunately I don't have access to Safari 6.1.x here, and I still can't
> replicate in Safari 6.0.5 or 7.0.4/5 – and given that only security updates
> and a sidebar were added, it seems almost certain that the issue is specific
> to your setup somehow. Re-opening but I'm not sure if there's anything we
> can do…

Well, I just updated my system to OS X 10.9.4 'Mavericks,' which contains Safari 7.0.5, and the menus *still* refuse to come out from underneath the content of any page that I might be trying to edit with VisualEditor.  (Speaking of this component, why did you change this bug's summary to indicate that it's a bug in OOJs rather than a bug in VisualEditor?  Is VisualEditor partly implemented OOJs, and do you suspect that this part of its implementation may be causing me my problems with VisualEditor?)  So, you may be right that my seeing this bug has something to do with my setup.  Do you want me to disable my Extensions again and empty my caches and then try using VisualEditor again?  How about re-enabling Safari's Extensions framework without enabling any of my installed extensions and then troubleshooting my installed extensions one by one to see which one causes the error?  I'll attach any error messages that pop up in my console when I run that test to this bug if you have me do so.  In addition, should I maybe contact either Apple or the developer of whichever Extension turns out to be the culprit and ask them to help us squash this bug once we figure out what's going on here?  I'd really *love* to solve this problem; it's driving me *nuts* that I can't use VisualEditor properly!