Settings not working, and layout issues.

What version of the base theme are you using?

Have you tried to run the DEV version of AT Commerce?

I will retest with iPhone later today, currently my iPhone has been "appropriated"... (ie one of my mates has decided he likes it more than me...).

Location map does not display maps in firefox or IE

What do you mean by "location map"? I need to know what type of map, how this is being rendered, what module etc etc. Ideally I need a link to a page showing the error.

@media queries only work on android devices at this time.

Media queries work in iOS browsers perfectly (most certainly Safari). They also work on FF & Opera on all platforms, IE9 and up etc etc.

Just ran tests with iPhone on the demo site - I got no problems, so I will need more information if you are having a problem.

There is no way to disable layouts, not easily anyway. The theme is designed to respond to these different device sizes and to do this in an optimal way (less code, really fast), so its a one way street for the most part.

The textures thing is fixed, I just havent committed it yet, but will shortly along with some other fixes. The textures apply to the Feature and Quint Panel regions.

The main menu is meant to stack.

Don't assign things to yourself please unless you are actually working on the solution - meaning you are writing a patch. I take you aren't, so it must be assigned to anon.

The map issue can be fixed with this CSS:

#locationmap_map img {
  max-width: none !important;
}

This is a known problem with all mapping solutions - in at.base.css there is a block of selectors that fix this for most other mapping solutions:

/* Override max-width 100% for map displays */
.gmap img,
.view-gmap img,
.openlayers-map img,
#getlocations_map_canvas img {
  max-width: none !important;
}

I'll add this locations_map one so its included in the next release (coming very shortly).

With regards to device width etc, the theme does not care about devices, only screen width - I know what you mean with the orientation stacking inconsistency, but when I look at this on iPhone it seems to make sense with regards to the actual look of it.

Its possible a more complex media query could negate this (say using device width) but I have deliberately kept the media queries very simple (so they will work in legacy devices supported with respond.js).

All these pointy/clicky solutions are 80 - 90% solutions, they are never going to be perfect, not given the sheer complexity and range of devices that must be accounted for - its all just a very generic approach that mostly works most of the time.

It will be ready when its ready.

Stop changing issue details!