Actinic V10 CSS Issues

[mediamole]

Hi,

Just incase nobody has spotted them already. There are one or two coding bugs in Actinic's own CSS.

When using the Clean CSS Layout theme the following CSS bug was spotted:

div.CheckoutCartSection {
	margin-top; 0px;
	margin-bottom: 10px;
}

Should be:

div.CheckoutCartSection {
	margin-top: 0px;
	margin-bottom: 10px;
}

[Darren B]

Thats not an easy one to spot - nice job

[brucet]

Thanks for reporting, this will be fixed in the second v10 maintenance release. It wasn't quite in time for the first.

[mediamole]

No problem. I've got my eagle eye CSS hat on I've only started developing in Actinic V10 over a week ago, so missed the opportunity to play with the BETA release.

I did spot this one also:

.checkout-field-input {
	width: *;
}

But wasn't sure if it was some weird CSS hack? Which I doubt as it appears to do nothing.

[mediamole]

Sorry and this one:

#bobcat-navigation-bar ul {
	margin: 0 5px;
	padding: 0;
	list-style: 0;
}

List-Style can't have a value of 0. Should be:

list-style: none;

[mediamole]

Same list-style bug appears here too:

#minimal-navigation-bar ul {
	margin: 0;
	padding: 0;
	list-style: 0;
}

[brucet]

Stoooooop! We surrender.....!
:-P

[leehack]

Any chance of delaying the release of 10.0.1 for a further 10 mins so these very simple fixes can be included please?

[mediamole]

That's all folks!

I didn't find anymore. And only spotted them as I have my first Actinic 10 site near ready to go live, and was playing around with the Shopping cart CSS

[pinbrook]

It would be a good idea for Actinic to have a css "expert" go over and validate all css, just to be sure - its basic stuff

[Darren B]

Stoooooop! We surrender.....!
:-P

LMFAO thanks Bruce

[brucet]

Every code change, css included, is normally checked before a release. The problem is not usually the knowledge, but there is an awful lot of code, it's a tedious and thankless task requiring loads of concentration, and lapses sometimes happen. :-(

Something obviously went particularly awry with the css for the new checkout, though. So having an independent pair of eyes looking through one discreet element like the css has been - patently - very helpful. Thanks Garry.

If it was simply matter of changing the code, we could fix this in v10.0.1. But we also have to review the changes, modify the upgrader, rebuild the executables, and then test everything. It would delay the release for an awful lot more than 10 minutes, I'm afraid...

[Sean Williams]

If it was simply matter of changing the code, we could fix this in v10.0.1. But we also have to review the changes, modify the upgrader, rebuild the executables, and then test everything. It would delay the release for an awful lot more than 10 minutes, I'm afraid...

I'm so amazed at this, I can't bring myself to say anything apart from

[malbro]

If it was simply matter of changing the code, we could fix this in v10.0.1. But we also have to review the changes, modify the upgrader, rebuild the executables, and then test everything. It would delay the release for an awful lot more than 10 minutes, I'm afraid...

Could you post a corrected css file in the download area