-
[TOPP trac] #2648: Wordpress Xinha layout messed up on openplans.org
from "The Open Planning Project"on 2008-06-27 19:31 #2648: Wordpress Xinha layout messed up on openplans.org ---------------------------+------------------------------------------------ Reporter: pw | Owner: egj Type: defect | Status: new Priority: critical | Milestone: Component: [unspecified] | Version: irie!!! (live on www.openplans.org) Keywords: | Confirmation: Blockedby: | Time_to_complete: Blocking: | ---------------------------+------------------------------------------------ To reproduce: go to a blog edit page, like http://www.openplans.org/projects/opencore/blog/wp-admin/post-new.php Notice that the right menu stuff is totally obscured by the xinha editor so you can't modify categories or any of the other stuff that's in the right menu. Tested in firefox 2.0 / linux. rmarianski saw the same thing on his mac. stage.openplans.org currently has the same behavior. -- Ticket URL: <http://trac.openplans.org/openplans/ticket/2648> The Open Planning Project <http://www.openplans.org> Trac - The Open Planning Project- Thread Outline:
-
- Re: [TOPP trac] #2648: Wordpress Xinha l ... by "The Open Planning Project" <opencore-bugs@...>
- Re: [TOPP trac] #2648: Wordpress Xinha l ... by "The Open Planning Project" <opencore-bugs@...>
- Re: [TOPP trac] #2648: Wordpress Xinha l ... by "The Open Planning Project" <opencore-bugs@...>
- Re: [TOPP trac] #2648: Wordpress Xinha l ... by "The Open Planning Project" <opencore-bugs@...>
- Re: [TOPP trac] #2648: Wordpress Xinha l ... by "The Open Planning Project" <opencore-bugs@...>
-
Re: [TOPP trac] #2648: Wordpress Xinha layout messed up on openplans.org
from "The Open Planning Project"on 2008-07-18 18:10 #2648: Wordpress Xinha layout messed up on openplans.org ----------------------------------+----------------------------------------- Reporter: pw | Owner: egj Type: defect | Status: new Priority: critical | Milestone: Component: [unspecified] | Version: irie!!! (live on www.openplans.org) Resolution: | Keywords: Confirmation: | Blockedby: Time_to_complete: | Blocking: ----------------------------------+----------------------------------------- Comment(by cpatterson): I'll look more over the weekend, but when I hit http://www.openplans.org/projects/opencore/blog/wp-admin/post-new.php? firefox is complaining about {{{ uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMScreen.width]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://piwik.openplans.org/piwik.js :: _pk_getUrlLog :: line 98" data: no] }}} I know that piwik is totally separate from xinha, but is it possible that failure is causing javascript processing to stop before xinha gets the appropriate width? (Alternatively, could it be the case that xinha is also failing to get the correct element width, but catches the exception?) {{{ #!html <div class="thumbnail"><a href="http://skitch.com/dimmerswitch/t8b5/firefox-2-osx-leopard-xinha- renderbug"><img src="http://img.skitch.com/20080718-mk3dn25shh2hu2pjx31fxuj2ty.preview.jpg" alt="firefox-2-osx-leopard-xinha-renderbug" /></a></div> }}} -- Ticket URL: <http://trac.openplans.org/openplans/ticket/2648#comment:1> The Open Planning Project <http://www.openplans.org> Trac - The Open Planning Project -
Re: [TOPP trac] #2648: Wordpress Xinha layout messed up on openplans.org
from "The Open Planning Project"on 2008-07-18 19:40 #2648: Wordpress Xinha layout messed up on openplans.org ----------------------------------+----------------------------------------- Reporter: pw | Owner: egj Type: defect | Status: new Priority: critical | Milestone: Component: [unspecified] | Version: irie!!! (live on www.openplans.org) Resolution: | Keywords: Confirmation: | Blockedby: Time_to_complete: | Blocking: ----------------------------------+----------------------------------------- Comment(by jab): just wanted to add that i'm also seeing this on my mac in firefox 3, camino, opera, and safari. i'd be curious to know what broke this. -- Ticket URL: <http://trac.openplans.org/openplans/ticket/2648#comment:2> The Open Planning Project <http://www.openplans.org> Trac - The Open Planning Project -
Re: [TOPP trac] #2648: Wordpress Xinha layout messed up on openplans.org
from "The Open Planning Project"on 2008-07-20 17:03 #2648: Wordpress Xinha layout messed up on openplans.org ----------------------------------+----------------------------------------- Reporter: pw | Owner: cpatterson Type: defect | Status: assigned Priority: critical | Milestone: Component: [unspecified] | Version: irie!!! (live on www.openplans.org) Resolution: | Keywords: Confirmation: | Blockedby: Time_to_complete: | Blocking: ----------------------------------+----------------------------------------- Changes (by cpatterson): * owner: egj => cpatterson * status: new => assigned -- Ticket URL: <http://trac.openplans.org/openplans/ticket/2648#comment:3> The Open Planning Project <http://www.openplans.org> Trac - The Open Planning Project -
Re: [TOPP trac] #2648: Wordpress Xinha layout messed up on openplans.org
from "The Open Planning Project"on 2008-07-20 17:03 #2648: Wordpress Xinha layout messed up on openplans.org ----------------------------------+----------------------------------------- Reporter: pw | Owner: cpatterson Type: defect | Status: closed Priority: critical | Milestone: Component: [unspecified] | Version: irie!!! (live on www.openplans.org) Resolution: fixed | Keywords: Confirmation: | Blockedby: Time_to_complete: | Blocking: ----------------------------------+----------------------------------------- Changes (by cpatterson): * status: assigned => closed * resolution: => fixed Comment: Closed by r19268. Since the toolbar is an absolutely positioned element (rather than floated), there will be the chance that it can overlap the footer when in an expanded state. If that is happening with any real frequency we should look at changing that column to use floats. I didn't do that now because I suspect that will be an edge case, and I didn't want to make intrusive changes without *really* thorough testing. -- Ticket URL: <http://trac.openplans.org/openplans/ticket/2648#comment:4> The Open Planning Project <http://www.openplans.org> Trac - The Open Planning Project -
Re: [TOPP trac] #2648: Wordpress Xinha layout messed up on openplans.org
from "The Open Planning Project"on 2008-07-22 12:27 #2648: Wordpress Xinha layout messed up on openplans.org ----------------------------------+----------------------------------------- Reporter: pw | Owner: cpatterson Type: defect | Status: closed Priority: critical | Milestone: Component: [unspecified] | Version: irie!!! (live on www.openplans.org) Resolution: fixed | Keywords: Confirmation: | Blockedby: Time_to_complete: | Blocking: ----------------------------------+----------------------------------------- Comment(by rmarianski): Yea just to comment on the absolute positioning, the reason we did that was because we wanted those to be on the sidebar, but *still* within the form. (Previously we had used deliverance to move those out, but then they weren't submitting because they weren't in the form any more) Absolutely positioning was the fastest/easiest solution. -- Ticket URL: <http://trac.openplans.org/openplans/ticket/2648#comment:5> The Open Planning Project <http://www.openplans.org> Trac - The Open Planning Project