You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Did you search for similar issues before submitting this one?
Yes.
Describe the issue you encountered:
On current master with devtools open there is a warning about us using l10nid as a prop on native elements such as span and div. This probably comes from refactors as we've switched from a custom element to a standard one.
Expected behavior:
All standard elements should get data-l10n-id's instead of l10nid
Platform (Win7, 8, 10? macOS? Linux distro?):
macOS
Brave Version:
Building in development mode.
Steps to reproduce:
Pull Master
npm watch and start
open the developer console (shift+f8)
Screenshot if needed:
Any related issues:
The text was updated successfully, but these errors were encountered:
Did you search for similar issues before submitting this one?
Yes.
Describe the issue you encountered:
On current master with devtools open there is a warning about us using l10nid as a prop on native elements such as span and div. This probably comes from refactors as we've switched from a custom element to a standard one.
Expected behavior:
All standard elements should get data-l10n-id's instead of l10nid
Platform (Win7, 8, 10? macOS? Linux distro?):
macOS
Brave Version:
Building in development mode.
Steps to reproduce:
Screenshot if needed:
The text was updated successfully, but these errors were encountered: