• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Item6122: TablePlugin precedence handling is flawed if a custom css (e.g. from a custom skin) is involved.

Item Form Data

AppliesTo: Component: Priority: CurrentState: WaitingFor: TargetRelease ReleasedIn
Extension TablePlugin Normal New   n/a  

Edit Form Data

Reported By:
Applies To:
Current State:
Waiting For:
Target Release:
Released In:


Precedence handling in TablePlugin seems flawed in case a custom css file (e.g. as part of a custom skin) setting table properties is involved. According to the docs, the precedence should be this (from most important): TABLE{} settings, custom css, TABLEATTRIBUTES settings (e.g. from TWikiPreferences). A problem arises if a table property (like borders) is set through both TABLEATTRIBUTES (e.g. by setting tablerules to none") and, differently, through the css file (eg. setting border: solid for table.td there). As documented, the css settings take precedence, resulting in a table with rules. If one tries to change that for one single table by adding a =TABLE settings giving tablerules none, that setting will simply be ignored.

From a short glance at the code I suggest the following happens: When processing the TABLE setting, TWiki first looks if there is an equal setting in TABLEATTRIBUTES, in which case nothing is done. But in this case the css setting (which is different from both TABLE and TABLEATTRIBUTES) wins, resulting in unwanted behavior.

-- TWiki:Main/MichaelRitter - 10 Nov 2008

Hi Michael, could you post an example where this happens, and a description of what should happen?

-- TWiki:Main.ArthurClemens - 10 Nov 2008

Summary TablePlugin precedence handling is flawed if a custom css (e.g. from a custom skin) is involved.
ReportedBy TWiki:Main.MichaelRitter
Codebase 4.2.2
SVN Range

AppliesTo Extension
Component TablePlugin
Priority Normal
CurrentState New


TargetRelease n/a

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r2 - 2008-11-10 - ArthurClemens
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback