Be careful with the advice of simply removing the flag by overriding
the JSP. The flag you are seeing below the field is because it is a
field (likely service builder) that is marked as
"localized". Chances are it is being rendered as the result
of the <liferay-ui:inpute-localized/> (I can't recall off hand
if there is also an attribute on input fields that might drive this,
you'd have to check).
Liferay does have qutite a number of small fragments that are reused
in more than a few places so you need to be careul in these scenarios
that you don't end up getting rid of the flag in more than one place.
You should also consider the fact that the backend for localized
fields doen't operate the same way as it does for a regular input, so
simple making it a text field might actually break the save/update functionality.
I would probably advocate for adding a custom class to the input
field in the file where it is used and use that css class to simply
HIDE it. To me that is the best option because it is not as invasive
as removing something from the product. It has the added benefit of
continuing to render the field so using devtools in the browser you
will be able to see the item and see the css (hidden flag) applied to
it. If someone is expecting to see it, and they don't even see it in
the source, it might cause great confusion.
Just my two cents -- you should always try to think of the next guy.
