13744 2007-05-15 17:30:17 -0700 WordPress Editor: Master Bug 2010-06-08 17:18:05 -0700 1 1 1 Unclassified WebKit HTML Editing 523.x (Safari 3) All OS X 10.4 RESOLVED FIXED InRadar P2 Normal --- 13743 13746 14350 21274 1 justin.garcia webkit-unassigned ap jgpippin soup webkit oldest_to_newest 9868 0 justin.garcia 2007-05-15 17:30:17 -0700 http://wordpress.com/ Login with thabih/79f5587 Click on New Post in the top left <rdar://problem/5191694> WordPress Editor: Master Bug 86052 1 webkit 2008-07-16 05:38:06 -0700 All blocking bugs are already fixed. I think the meta bug should be fixed, isn't it? 86071 2 justin.garcia 2008-07-16 10:51:43 -0700 There is https://bugs.webkit.org/show_bug.cgi?id=17993 but it's not exactly blocking this bug anymore since it doesn't happen with current versions of WordPress (post 2.5). We are tracking some WordPress editor bugs internally. I'm going to check and see if any of those are still reproducible... 115648 3 jgpippin 2009-03-27 18:35:32 -0700 REGRESSION: In TinyMCE (observed environment: Wordpress 2.7.1 post edit with visual editor turned ON), using various javascript-driven "pop ups" generates odd behavior; namely, the window only partially rendering (just the header and footer). This behavior is exhibited in r41944, but was NOT exhibited in r41894. REPRO: Create a new post in a Wordpress installation (in Visual, not HTML mode), highlight some text and attempt to use the link button to assign a link to this test. Presumably, any instance of TinyMCE should be able to reproduce this bug, since Wordpress pretty directly implements TinyMCE. 235522 4 soup 2010-06-08 14:18:55 -0700 WordPress version 2.9.2 Visual Editor content is not visible in Webkit Nightly build version r60820. WordPress HTML editor is not affected. 235595 5 ap 2010-06-08 17:18:05 -0700 That's probably bug 40292, which will be fixed in the next nightly. I don't think that this bug is helpful any more - all dependencies have been resolved, so all it does is confuse people into reporting new issues here, where they can easily be overlooked. Re comment 3 - please file a new bug about that, if it still happens. Sorry for overlooking your report, it's been in an old bug, so I didn't see it.