I understand, if you call it a feature it doesn't fall under bug protocol.
If you install CS6 on a new XPS 15. it is not usable. The UI elements are not readable without a magnifying glass. You can call it fully functional if you want, but it is not usable. Big difference. The 200% would not have been done had it not been for the problem, period. The "feature" is not necessary, nor even useful had it not been the problem. If you can't call it a bug because that puts Adobe in a different position, that's a business decision, I get it.
You can keep saying the same thing. Using analogies that aren't valid (Ford). Or, thinking effort has something to do with making it not a bug (previous post). etc.
The fact is, if Ford sold me last years model and it was broken, they would have to fix it. If I can't use my newly purchased software on my XPS because the UI is too small to read and thus use, then it is broken.
You can call it a feature all you want but, it was decided to be done after, and because the Hi-res problem was discovered. Even your own people (Adobe) were/are calling it a bug. Now it's a "feature" that people are really only using for this problem. Fine.
Chris I/we would rather not hear from you on this anymore. You can't or wont call it a bug because that changes the conversation. I get it. Please honor my request, and have someone at a leadership level get back with us.
Thanks