#NaN on border-color when parsing rgb command line

[DataHerder]

FYI:

Say I use lessc on a file that simply has this class:

.random {
  border-color: transparent transparent transparent rgb(230,230,230);
}

It will output:

.random {
  border-color: #NaNbbaaNaN00NaN00NaN00NaN00NaN #NaNbbaaNaN00NaN00NaN00NaN00NaN #NaNbbaaNaN00NaN00NaN00NaN00NaN #e6e6e6;
}

However this will not happen if I run it on this:

.random {
  border-color: transparent transparent transparent #e6e6e6;
}

I have tested this on "color" as well so I think this is a global issue.

[DataHerder]

It also does this on background: transparent url('');

[phiamo]

can confirm, merging #800 breaks also compiling of twitters bootstrap2 ...
unusable atm :(

[lukeapage]

Amazing that of all the great pull requests to include a dud one was included and now.. Silence..

[DataHerder]

I really want to see Less.js stay around. I immensely enjoy this contribution.

[taeram]

I'd also love to see this one fixed right away. We're updating less to the latest on a regular basis, and we're having to force a checkout of an earlier version to prevent this issue.

👍 to merge pull request #806, reverting changes in pull request #800

[dfjones]

+1 to revert #800

This change is really bad and has been shown to break a lot of existing code.

[sturobson]

I've just tried this w/ latest LESS.js app and it outputs as expected with no errors. Can you confirm how you're compiling?

[dfjones]

Don't use the app. Clone this repo, and use /bin/lessc

[lukeapage]

this was reverted, so should be fine now and some of us are working on sorting things out.