Last modified: 2014-10-06 22:18:15 UTC
Created attachment 15204 [details] A screenshot indicating where exactly between the VisualEditor toolbar and the content being edited with VisualEditor the 'Insert' menu becomes hidden under such content being edited As shown in the attached screenshot, attempting to open VisualEditor's 'Insert' menu causes it to open behind the content of the page that you have opened within VisualEditor. This occurs when VisualEditor is used in Safari 6.1.3 under OS X 10.8.5 'Mountain Lion' when this OS is run on a mid-2007 aluminum iMac with a 2.4-GHz Intel Core 2 Duo processor, 4 GB of 667-MHz DDR2 SDRAM, and an ATI Radeon HD 2600 Pro with 256 MB of dedicated VRAM. For some reason, though, this bug has been somewhat intermittent over the past month or so (it showed up for a while at first, then appeared as if it had been fixed before whatever patch that fixed it was reverted or otherwise messed with.) Is my bug a duplicate of another one even though I couldn't find a similar one via Bugzilla's search mechanism? If so, have there been notices in the comments of this other bug about its status?
What skin are you using, and do you have any gadgets or local user scripts or styling that might be competing?
Yes; I have several modifications installed as modifications both to my local copy of Safari and to my Wikipedia account (I was experiencing this bug on the English WP.) In Safari, I have the 'Duplicate Tab' Button 2.0, Print Plus 1.1.0.2, Middle-Click AutoScroll 1.04, TabLock 1.1, Search Preview 1.2.3, Tab Reloader 1.5.2, Session 1.3.0.2, Feedly 16.0.5.21, and Ultimate Status Bar 1.3 extensions installed and enabled and the Cuss Off 1.1, MacRumors Minimal 1.7, and Lazarus Form Recovery 3.2 extensions installed, but disabled. The en:wp Gadgets that I have enabled in my preferences are, as listed on en:wp:Special:Gadgets, Gadget-searchFocus.js, Gadget-ImageAnnotator.js, Gadget-imagelinks.js, Gadget-popups.js/Gadget-navpops.css, Gadget-PrintOptions.js, Gadget-revisionjumper.js, Twinkle, Gadget-HideFundraisingNotice.js/Gadget-HideFundraisingBanner.css, Gadget-teahouse.js/Gadget-teahouse.css, Gadget-WatchlistChangesBold.js/Gadget-WatchlistChangesBold.css, Gadget-defaultsummaries.js, Gadget-citations.js, Gadget-HotCat.js, Gadget-wikEd.js, Gadget-afchelper.js, Gadget-DRN-wizard-loader.js, Gadget-edittop.js/Gadget-edittop.css, Gadget-UTCLiveClock.js, Gadget-mySandbox.js, Gadget-purgetab.js, Gadget-externalsearch.js, Gadget-dropdown-menus.js/Gadget-dropdown-menus.css, Gadget-CommentsInLocalTime.js, Gadget-NoSmallFonts.css, Gadget-metadata.js, Gadget-MenuTabsToggle.js/Gadget-MenuTabsToggle.css, Gadget-JustifyParagraphs.css, Gadget-righteditlinks.css, Gadget-PrettyLog.js/Gadget-PrettyLog.css, Gadget-SidebarTranslate.js/Gadget-SidebarTranslate.css, Gadget-widensearch.css, Gadget-DejaVu Sans.css, Gadget-contribsrange.js, Gadget-BugStatusUpdate.js, Gadget-RTRS.js, and Gadget-NewImageThumbs.js/Gadget-NewImageThumbs.css. The beta features that I am using on en:wp are 'New search,' 'Media Viewer,' 'VisualEditor,' 'VisualEditor formulae editing,' and 'Compact language links.' (Maybe I should open another new bug labeled as an 'enhancement' asking for users to have the ability to export their Gadget and Beta Features settings as a CSV file so that they don't have to type them all out when they need to submit them as pieces of technical information for help with bugs?)
I've just found out that this bug also occurs for another menu (the 'Formatting' one — that's what the menu with an icon that looks like an underlined capital 'A' is called, right?) at en:meta under my user environment. I'll update this bug with my results as I try and use other menus in VisualEditor at other wikis.
Has this been fixed yet, or did everybody forget about me?
(In reply to Bryce Glover from comment #4) > Has this been fixed yet If it was fixed, the status of this ticket was RESOLVED FIXED. As long as only one user has ran into this issue and steps to reproduce are unclear, it's likely not a high priority.
Sorry for the brief delay. I am unable to reproduce this for default-setup users on the English Wikipedia in Safari 7.0.3, in default Vector or Monobook, or whilst logged in with fewer gadgets switched on. Though it's theoretically possible that there's a rendering difference between Safari 6.1.3 and 7.0.3 in this respect, it's very unlikely, and I would assume the bug is caused by a browser plugin or a gadget. Given that you're getting the same behaviour on a different site (meta as well as enwiki), it's most likely to be a browser plugin issue (though none of your plugins look suspicious at first glance). Would it be possible for you to visit https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in Safari, and/or in a different browser, and see if it recurs?
(In reply to Andre Klapper from comment #5) > (In reply to Bryce Glover from comment #4) > > Has this been fixed yet > > If it was fixed, the status of this ticket was RESOLVED FIXED. > > As long as only one user has ran into this issue and steps to reproduce are > unclear, it's likely not a high priority. Ah, sorry; I was getting a little impatient, not to mention worried! I'm relatively new to Bugzilla, so, duh: I should have thought, "Oh! It hasn't been marked as 'RESOLVED FIXED' yet." Now I feel ignorant…heh, heh. (sheepish smile)
(In reply to James Forrester from comment #6) > Would it be possible for you to visit > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in > Safari, and/or in a different browser, and see if it recurs? Doing now…
(In reply to James Forrester from comment #6) > Would it be possible for you to visit > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in > Safari, and/or in a different browser, and see if it recurs? Yup; it still occurs even while I'm logged out of Wikipedia. I've also confirmed that all of the other menus ('Paragraph' — that's a styling menu, right? — and the ones labeled with a question mark inside of a circle — 'Help', maybe? — , a triangular warning sign — could this be 'Report a Problem?' — , and a column of stacked lines — I'm assuming that this means 'More Options') open with their menus tucked under the content of the page that is being edited with VisualEditor.
(In reply to Bryce Glover from comment #9) > (In reply to James Forrester from comment #6) > > Would it be possible for you to visit > > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in > > Safari, and/or in a different browser, and see if it recurs? > > Yup; it still occurs even while I'm logged out of Wikipedia. I've also > confirmed that all of the other menus ('Paragraph' — that's a styling menu, > right? — and the ones labeled with a question mark inside of a circle — > 'Help', maybe? — , a triangular warning sign — could this be 'Report a > Problem?' — , and a column of stacked lines — I'm assuming that this means > 'More Options') open with their menus tucked under the content of the page > that is being edited with VisualEditor. Thanks. I take it this is still with Safari 6.1.3 with all your plugins, whilst logged out?
(In reply to James Forrester from comment #10) > (In reply to Bryce Glover from comment #9) > > (In reply to James Forrester from comment #6) > > > Would it be possible for you to visit > > > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in > > > Safari, and/or in a different browser, and see if it recurs? > > > > Yup; it still occurs even while I'm logged out of Wikipedia. I've also > > confirmed that all of the other menus ('Paragraph' — that's a styling menu, > > right? — and the ones labeled with a question mark inside of a circle — > > 'Help', maybe? — , a triangular warning sign — could this be 'Report a > > Problem?' — , and a column of stacked lines — I'm assuming that this means > > 'More Options') open with their menus tucked under the content of the page > > that is being edited with VisualEditor. > > Thanks. I take it this is still with Safari 6.1.3 with all your plugins, > whilst logged out? That's right. Hold on, though; I forgot to check Firefox 17.0.1 (yeah, I know; I'll remind my dad to update it as soon as I can…)
(In reply to Bryce Glover from comment #11) > (In reply to James Forrester from comment #10) > > (In reply to Bryce Glover from comment #9) > > > (In reply to James Forrester from comment #6) > > > > Would it be possible for you to visit > > > > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in > > > > Safari, and/or in a different browser, and see if it recurs? > > > > > > Yup; it still occurs even while I'm logged out of Wikipedia. I've also > > > confirmed that all of the other menus ('Paragraph' — that's a styling menu, > > > right? — and the ones labeled with a question mark inside of a circle — > > > 'Help', maybe? — , a triangular warning sign — could this be 'Report a > > > Problem?' — , and a column of stacked lines — I'm assuming that this means > > > 'More Options') open with their menus tucked under the content of the page > > > that is being edited with VisualEditor. > > > > Thanks. I take it this is still with Safari 6.1.3 with all your plugins, > > whilst logged out? > > That's right. Hold on, though; I forgot to check Firefox 17.0.1 (yeah, I > know; I'll remind my dad to update it as soon as I can…) OK, I know that the version of Firefox which I mentioned (17.0.1) works just fine even when I'm logged in to Wikipedia as myself (I didn't see the 'Edit^[beta]' link when I wasn't,) so it's got to be something in Safari 6.1.3 that's going wrong.
Created attachment 15283 [details] Screenshot of no issue in Safari 6.0.5
(In reply to Bryce Glover from comment #12) > OK, I know that the version of Firefox which I mentioned (17.0.1) works just > fine even when I'm logged in to Wikipedia as myself (I didn't see the > 'Edit^[beta]' link when I wasn't,) so it's got to be something in Safari > 6.1.3 that's going wrong. That's unfortunate. I've tried it with Safari 6.0.5 and it works as expected; this is either a very odd problem with a sub-version of Safari (which is unlikely) or caused by a browser plugin. I don't really like to close such bugs as "WORKSFORME" but there's nothing much I can offer at this point, sadly…
Maybe I should disable my Extensions and then turn them back on one by one to figure out which one is causing the problem? That way, I could contact that plug-in's developer and discuss the bug with him or her.
(In reply to Bryce Glover from comment #15) > Maybe I should disable my Extensions and then turn them back on one by one > to figure out which one is causing the problem? That way, I could contact > that plug-in's developer and discuss the bug with him or her. Okay, guess what? It's apparently *Apple's* fault since this bug occurs for me with Extensions enabled (it goes away when they aren't — yay!) but (get this!) *no extensions enabled*. I'll attach what my error console gives me to this bug in a sec.
(In reply to Bryce Glover from comment #16) > (In reply to Bryce Glover from comment #15) > > Maybe I should disable my Extensions and then turn them back on one by one > > to figure out which one is causing the problem? That way, I could contact > > that plug-in's developer and discuss the bug with him or her. > > Okay, guess what? It's apparently *Apple's* fault since this bug occurs for > me with Extensions enabled (it goes away when they aren't — yay!) but (get > this!) *no extensions enabled*. I'll attach what my error console gives me > to this bug in a sec. Sorry about changing the bug status; I thought that doing so would bring back the 'UNRESOLVED' option so that I could attach a picture of my browser's console logs for that page to which you sent me a link. Could somebody un-'RESOLVED WONTFIX' this for me so that I can do this, or am I on my own here?
The "Add an attachment" link should work, unrelated to bug status.
(In reply to Andre Klapper from comment #18) > The "Add an attachment" link should work, unrelated to bug status. Oh, wait; I see it, but it moved from below the 'Additional Comments:' dialog box to below the list of attachments to this bug at the top of the page. Stupid me; I should have looked first!
Created attachment 15289 [details] Safari 6.1.3 JavaScript Console Logs for https://en.wikipedia.org/wiki/Foobar?veaction=edit As this title says, this attachment contains the JavaScript console logs which Safari 6.1.3 running on OS X 10.8.5 'Mountain Lion' provided for the URL 'https://en.wikipedia.org/wiki/Foobar?veaction=edit'.
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!)
(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…
*** Bug 67741 has been marked as a duplicate of this bug. ***
(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!
P. S.: I just looked at the duplicate bug, number 67741, and I realized that I *always* zoom in by two levels when I use Wikipedia! I will therefore check to see if VisualEditor works normally when I'm not zoomed in at all before you guys have me do any deeper testing, all right?
P. P. S.: It turns out that VisualEditor's menus load properly if you reset Safari's zoom level before clicking on 'Edit [beta]' even if you then zoom in afterwards! Crazy, right?
Any progress on fixing the zooming issue?
I'd love to help but I don't own a Mac. :(
Ah, I see; that *would* be a problem since Apple no longer supplies current versions of Safari to Windows users. It seems to me, however, that this bug has been fixed for users of Safari 7.1 (9537.85.10.17.1), to which I updated a little while back, by recent changes to either WebKit or the MediaWiki software. Since I no longer have either Safari 6.1.3 or Safari 7.0.5, could anybody check to see if this bug still exists for those versions of Safari?
Assuming that the steps to reproduce are: 1. Read Wikipedia article in Safari. Zoom in at least twice (Command-+). 2. Open page in VisualEditor. 3. Click on drop-down menus (e.g., the character formatting menu). then I cannot reproduce this today in Safari 6.2 on Mac OS 10.8.5.
@WhatamIdoing: Methinks that the problem is highly exacerbated by the use of Safari Extensions (see comment 2 for the full list of stuff I had on my computer when this bug first appeared for me.)
