mahara-contributors team mailing list archive

[Melissa Newman <1264098@xxxxxxxxxxxxxxxxxx>]

The discussion is simple ... everything that is a valid css property
should be allowed.  CSS does not cause malicious code, so there is
absolutely no reason why it needs to be filtered.  And if somebody does
something that causes an affect the user does not want (white text on a
white background), simply include a button that either allows the page
to be be temporarily set to default settings or revert to the last saved
settings.

Mahara's main problem is that Mahara tries to hold the hand of the user
too much.  There is a point in trying to help the user by making things
easier, but when the help frustrates the user, the help is of no help.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1264098

Title:
  skins not saving properly

Status in Mahara ePortfolio:
  Confirmed

Bug description:
  I tried to create a new skin with custom CSS code added to the
  "Advanced" tab.

  collection-nav ul {
    columns: 2;
    -webkit-columns: 2;
    -moz-columns: 2;
  }

  When I save it, and then try to edit the skin, everything is deleted
  except:

  ul {
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1264098/+subscriptions