Quote:
Originally Posted by anamardoll
Speaking as a technical writer, this. 
Documenting a bug does not make it a feature. It IS good to document it so that the customer has a chance at realizing that the bad behavior is KNOWN bad behavior, but it is still a bug.
I think it very unlikely that the NC highlighting feature was implemented this way on purpose, with a specific use case in mind.  |
You are mistaken. When developing software, you are given a set of requirements, and the final goal is for the software to fulfill those requirements. If you do not like how a feature behaves, but that feature adheres to the requirements, then you do not have a bug. You would then submit a change request to have the requirements updated, so the feature can behave in a different way.
I'm not saying that this feature works as I would want it to work, I am just saying that it works as it was intended to work, hence it is not a bug.