mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

** Also affects: mahara/1.10
   Importance: Undecided
       Status: New

** Also affects: mahara/1.8
   Importance: Undecided
       Status: New

** Also affects: mahara/1.9
   Importance: Undecided
       Status: New

** Changed in: mahara/1.10
    Milestone: None => 1.10.1

** Changed in: mahara/1.8
    Milestone: None => 1.8.6

** Changed in: mahara/1.9
    Milestone: None => 1.9.4

** Changed in: mahara/1.10
   Importance: Undecided => High

** Changed in: mahara/1.8
   Importance: Undecided => High

** Changed in: mahara/1.9
   Importance: Undecided => High

-- 
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/1394330

Title:
  Improper use of the parseInt javascript function

Status in Mahara ePortfolio:
  In Progress
Status in Mahara 1.10 series:
  New
Status in Mahara 1.8 series:
  New
Status in Mahara 1.9 series:
  New

Bug description:
  The parseInt() function needs to specify that it is using radix 10

  Older browsers use the octal radix (8) as default so parseInt('010')
  will return '8' rather than '10' that we might expect.

  In many places the function is used correctly, eg: parseInt(match[1],
  10);

  But not all places are indicating to use a base 10 radix.

  So I'll clean up the places it is not used so that we know to return a
  base 10 number.

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