Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
markup
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Feb 2010 at 05:12 UTC
Updated:
6 Sep 2011 at 02:54 UTC
Jump to comment: Most recent file
Comments
Comment #2
jacineComment #3
sivaji_ganesh_jojodae commentedThe patch looks good for me, adds appropriate class but the test case fails irrespective of patch.
Comment #4
berdirThis should pass the test. the classes were not always passed as an array.
Comment #6
berdirWow, that's quite a mess. Looks like a random mix of string and array class definitions to me. Tried to unify but I'm just gessing if that's really the intended behaviour now... Someone needs to confirm that :) I clicked through the different versions produced by the test and it looked good to me.
The tests should really pass this time..
Comment #7
jacine#6: update-version-table2.patch queued for re-testing.
Comment #8
jacineHey, thanks for the patch @Berdir! It looks good to me, minus one little nit pick:
Can we just call leave this as $version_class instead of adding $security_class? Unless I'm missing something, it's really still just another version class, right? ;)
Powered by Dreditor.
Comment #9
jacine#6: update-version-table2.patch queued for re-testing.
Comment #11
jacineJust checked and this is no longer a problem.