Why aren't ecommerce UI fixes consider bugs?
In general, bug designation is reserved for core code base. The TitleLeaf development team is continually updating server operating systems, programming languages, web frameworks et al to ensure this core code works with new devices and browsers. TitleLeaf subscriptions subsidize the maintenance of this core code. If some part of that code isn’t working properly, the TitleLeaf team will resolve it without further cost to you.
This is in contrast to a client's public user interface (aka, your ecommerce “theme”) which is not designated as core code. A theme is created per a time-limited, contractual setup agreement. It becomes the client’s property “as-is” upon contract completion (normally, triggered by site launch).
To adjust the theme, a client submits a service request. The client is billed for the time needed to resolve the request.
TitleLeaf does not guarantee that the original theme code or the adjustments will function properly with modern browsers in perpetuity. In other words, it is not maintained unless so requested.
The TitleLeaf team tries to ensure themes are as robust and future-proof as possible without making costs prohibitive. Defining that line between robustness and cost is subjective. TitleLeaf’s overarching goal is to provide services for competitive prices and reasonable expectations.