Google Chromebook: Difference between revisions
Scorpiomaj27 (talk | contribs) No edit summary |
m put incident under the right section with full citation |
||
| Line 8: | Line 8: | ||
| Logo = Chromebook-logo.png | | Logo = Chromebook-logo.png | ||
}} | }} | ||
==Consumer impact summary== | ==Consumer impact summary== | ||
| Line 42: | Line 34: | ||
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]]. | This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]]. | ||
{{Placeholder box|Replace the placeholder text in the sections below with the incidents that affect this product line and a short summary. Also replace the link so it point to the right company article.}} | {{Placeholder box|Replace the placeholder text in the sections below with the incidents that affect this product line and a short summary. Also replace the link so it point to the right company article.}} | ||
=== Google Chromebook Bricked after Force-installing a Hidden Extension === | |||
A certain hidden extension that was forcibly installed onto a Chromebook by Google essentially '''bricked that Chromebook.<ref name="CBrick">{{Cite web |last=Isaac |first=Rob |date=24 Mar 2025 |title=Today Google bricked my Chromebook by force-installing a hidden extension |url=https://news.ycombinator.com/item?id=43514087 |url-status=live |archive-url=https://web.archive.org/web/20250331115019/https://news.ycombinator.com/item?id=43514087 |archive-date=31 Mar 2025 |via=Hacker News, originally posted on Mastodon}}</ref>''' | |||
The user's complaint is that the machine has become hot and that the extra load has essentially made it unusable. | |||
===Example incident one (''date'')=== | ===Example incident one (''date'')=== | ||
{{Main|link to the main article}} | {{Main|link to the main article}} | ||
| Line 62: | Line 59: | ||
[[Category:{{PAGENAME}}]] | [[Category:{{PAGENAME}}]] | ||
[[Category:Anti-Consumer Practices]] | [[Category:Anti-Consumer Practices]] | ||
[[Category:Planned obsolescence]] | [[Category:Planned obsolescence]] | ||
Revision as of 08:58, 21 June 2025
⚠️This article has been marked as incomplete. Sourcing or verifiability needs additional work.
#appeals channel in either Zulip or Discord to request removal.Articles must provide verifiable, credible evidence for their claims and avoid relying on forum posts, personal blogs, or other unverifiable sources. You can help by replacing weak citations with reputable reporting, corporate communications, receipts, repair logs, or independent investigative coverage that demonstrates the systemic relevance required by the Mission statement and Moderator Guidelines.
| Basic Information | |
|---|---|
| Release Year | 2011 |
| Product Type | Software/Hardware |
| In Production | Yes |
| Official Website | Google Chromebook |
Consumer impact summary
| Overview of concerns that arise from the conduct towards users of products part of the product line. |
Touch on relevant topics like:
|
Incidents
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the Google Chromebook category.
Google Chromebook Bricked after Force-installing a Hidden Extension
A certain hidden extension that was forcibly installed onto a Chromebook by Google essentially bricked that Chromebook.[1]
The user's complaint is that the machine has become hot and that the extra load has essentially made it unusable.
Example incident one (date)
- Main article: link to the main article
Short summary of the incident (could be the same as the summary preceding the article).
Example incident two (date)
...
Incidents affecting all of the company's products can be found in the company article: Company article
Products
See also
References
- ↑ Isaac, Rob (24 Mar 2025). "Today Google bricked my Chromebook by force-installing a hidden extension". Archived from the original on 31 Mar 2025 – via Hacker News, originally posted on Mastodon.