Ticket #6369 (closed Bug: fixed)

Opened 7 years ago

Last modified 2 years ago

RTL- History table - headers align

Reported by: oferw Owned by: oferw
Priority: minor Milestone: 3.3.x
Component: RTL Version: 4.1
Keywords: TuneUp54 Cc:

Description

The headers align should be in the center and not to the left

Attachments

Screenshot5.jpg Download (25.9 KB) - added by oferw 7 years ago.
History table align - Ofer Weisglass

Change History

Changed 7 years ago by oferw

History table align - Ofer Weisglass

comment:1 Changed 7 years ago by oferw

should be this in the css fix (table align to the right)

<table summary="סריקת הסטוריה" class="listing nosort" align=right>

comment:2 Changed 7 years ago by hannosch

  • Owner changed from hannosch to oferw
  • Component changed from Internationalization to RTL

comment:3 Changed 5 years ago by emanlove

Ofer, is the attached screenshot Download showing the history under NuPlone? As far as I can tell under the 3.2 branch (r24743) this is woorking correctly (i.e. the history table headers are center aligned) with plain Plone site. But under RTL NuPlone , again the 3.2 branch) the headers are left aligned. Comparing this to the headers under LTR NuPlone the headers are aligned left.

Given there left aligned under LTR NuPlone (and not centered), am I correct in saying under RTL NuPlone they should be right-aligned?

comment:4 Changed 2 years ago by emanlove

  • Keywords TuneUp54 added
  • Status changed from new to closed
  • Version set to 4.1
  • Resolution set to fixed

This issue has been reported fixed starting in Plone version 3.2. Under the current major version of Plone 4.x the history presentation has changed and this issue is no longer valid. If you are using an older version of Plone and this issue is still a problem for you, you can find support from the Plone community through our mailing lists, chat room, the Plone section on Stack Overflow, and various other support channels. For more information about community support see  http://plone.org/support.

Note: See TracTickets for help on using tickets.