1.7.1 is on the store.
DocKnight, two of your three are fixed, and you were right about both, including the cause of the second one.
The details on a phone
You were right that 1.6.0 did not fix this. It moved the details out of the very bottom but left them under the whole sidebar, which on a phone is still a long way down. I had the measurement in front of me when I shipped it, the details sat at 1715 pixels against the price at 874, and I did not look hard enough at my own numbers. They now come straight after the price with nothing wedged in between.
The reason my test did not catch it is worth saying out loud: it checked that the stylesheet contained the ordering I had written, not where things actually landed on a screen. It has been replaced with one that drives a real browser at 390 pixels wide and reads the position of every block. I then broke the fix four different ways, including putting back the exact 1.6.0 arrangement, and confirmed the new test fails each time. It would have caught this.
The thumbnails that swallow the scroll
Your instinct about quick view was exactly right, and it was not the carousel at all.
There is an invisible Quick view link lying across the middle of every thumbnail. It is transparent but it was still catching the pointer, so a finger landing on a photo opened the quick view overlay, and that overlay stops the whole page scrolling until you tap back outside. That is your "till you unclick back outside of it", and it is also why you could reproduce it with a mouse. I had started down the wrong road fixing the carousel's wheel handling before I measured what was actually under the finger.
It is now inert while it is invisible and only becomes clickable once it is really shown, so Quick view still works as before if you mean to use it.
The custom field suggestion list
Not fixed, and I am not going to pretend it is close to done. It is next. It also turns out somebody else arrived this week with 6500 models in a single field, so this one has two forums behind it now rather than one, which is how it should be prioritised.
St. James, on freezing a listing
Half of what you need exists today and half does not, so here it is plainly.
What works now: a moderator with the approve and unapprove permission can unapprove a listing. It immediately disappears from the marketplace, from search and from everyone else's view. The staff can still see it, so it is not lost.
What does not work: the seller can still edit it and still delete it. Nothing stops them wiping the evidence the moment they realise they have been spotted. For a market with counterfeits in it that is the half that actually matters, and you have put your finger on a real gap rather than a missing setting.
So that is what I am building: a moderator hold that freezes a listing in place. Hidden from buyers, editing and deleting refused for the seller with a plain reason shown, and the staff keeping full access while they look into it. Lifting the hold puts it back exactly as it was.
On the graveyard idea: a hidden category does work today, because view permissions are set per category, so one that only the staff can see is a few clicks. It is just not airtight on its own at the moment, since an unfrozen seller can move or delete the listing before you get there. Hold first, then file it wherever you like, and the two together give you what you described.
And the ignore list
You are right, and it is worse than a bug: the add-on does not consult the ignore list anywhere at all. Somebody who has told you they want nothing to do with a seller still gets that seller's listings in their face. That is going in with the moderator hold.
No date on either, but they are the next two things I touch.
