fix: update private-protected-properties-methods article.md en #3915

Original file line number	Diff line number	Diff line change
Expand Up		@@ -186,11 +186,9 @@ So protected fields are naturally inheritable. Unlike private ones that we'll se

		## Private "#waterLimit"

	[recent browser=none]
	[recent browser="new"]

	There's a finished JavaScript proposal, almost in the standard, that provides language-level support for private properties and methods.

	Privates should start with `#`. They are only accessible from inside the class.
	Private properties and methods should start with `#`. They are only accessible from inside the class.

		For instance, here's a private `#waterLimit` property and the water-checking private method `#fixWaterAmount`:

Expand Down Expand Up		@@ -318,5 +316,3 @@ To hide an internal interface we use either protected or private properties:

		- Protected fields start with `_`. That's a well-known convention, not enforced at the language level. Programmers should only access a field starting with `_` from its class and classes inheriting from it.
		- Private fields start with `#`. JavaScript makes sure we can only access those from inside the class.

	Right now, private fields are not well-supported among browsers, but can be polyfilled.

Navigation Menu