Project

General

Profile

Bug #1546

Unable to view comparative document history in BP Docs

Added by Matt Gold over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority name:
Low
Assignee:
Category name:
BuddyPress (misc)
Target version:
Start date:
2012-01-13
Due date:
% Done:

0%

Estimated time:

Description

When viewing a comparative history of two versions of a BP Doc, one version is overflowing its div and is impossible to read. Please see the attached screenshot.

History

#2 Updated by Boone Gorges over 10 years ago

  • Status changed from Assigned to Reporter Feedback
  • Priority name changed from Normal to Low

I'm finding that, while the styling is not perfect, I'm unable to produce anything as radically wrong as what you're seeing. Please send a link to a live page where you see the problem, along with details about your setup.

#3 Updated by Matt Gold over 10 years ago

Here's a link . My setup: Mac OS X 10.7.2, Chrome 16.0.912.75 (up to date).

#4 Updated by Chris Stein over 10 years ago

FWIW, When I followed the link in Chrome I had the same problem.
Looking at it though, it's hard for me to imagine how the two versions could fit comfortable side-by-side in the space we have.

There are some times, and this may be one of them, when it would be nice to either allow the site to be wider than it is or somehow take it out of the normal layout (in this case two columns with the navigation on the left). It may mean something like showing it in a popover like is done for image galleries.

#5 Updated by Boone Gorges over 10 years ago

I messed with it for over an hour this afternoon and couldn't figure it out. Webkit seems to prerender tables based on content, and there's no way to override it with CSS. I think that the fix is going to be, as Chris suggests, allowing the readable page area to expand on this page. It's going to look pretty crummy, but at least it'll allow you to use the revision comparison.

#6 Updated by Boone Gorges over 10 years ago

  • Status changed from Reporter Feedback to Resolved

Turns out that my Chrome cache was just being really sticky. (Yet another reason I stopped using it.) Fixed in https://github.com/castiron/cac/commit/6fe8856021d49a1785fbc60bd9a7958228876c71

Also available in: Atom PDF