| Recurring |
one_organization |
(a) The software failure incident related to the blocking of autoplaying video with sound in Chrome by Google is an example of a similar incident happening again within the same organization. Google had initially rolled out the blocking feature in Chrome to address the issue of annoying autoplaying videos with sound on the web. However, this update ended up breaking a series of web apps, games, and interactive art, causing complaints from developers and users [71223].
The incident led Google to partially roll back the autoplay policy for the Web Audio API in Chrome 66, with plans to reapply the policy in Chrome 70 after giving developers more time to update their code. This situation highlights how even well-intentioned software updates can have unintended consequences, leading to the need for adjustments and temporary solutions within the same organization [71223]. |
| Phase (Design/Operation) |
design |
(a) The software failure incident in the article can be attributed to the design phase. The blocking feature introduced in Chrome to prevent autoplaying videos with sound ended up breaking a series of apps, games, and interactive art by preventing them from playing audio for alerts and other elements. This issue arose as a result of the update in Chrome 66, which implemented the autoplay policy for the Web Audio API. Developers and users of these interactive web apps raised complaints about the impact of this design change on their software [Article 71223].
(b) The software failure incident is not directly linked to the operation phase or misuse of the system. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident described in the article is primarily within the system. Google's Chrome browser had implemented a feature to block autoplaying videos with sound, which was intended to enhance user experience by preventing annoying videos. However, this update ended up breaking a series of web apps, games, and interactive art by interfering with the Web Audio API, causing them to lose audio functionality. The decision to temporarily roll back the autoplay policy for the Web Audio API was made internally by Google to give developers more time to update their code before reapplying the policy in a future version of Chrome [71223]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in this case was primarily due to non-human actions. Google had rolled out a feature in Chrome to block autoplaying videos with sound, which inadvertently affected a large collection of web apps and games, breaking their audio functionality. This change was not intentionally caused by human actions but rather by the implementation of the autoplay policy in Chrome [71223]. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident in the article was not attributed to hardware issues. It was related to a change in Chrome's autoplay policy that impacted web apps and games by breaking their audio functionality [71223].
(b) The software failure incident in the article was specifically due to a change in Chrome's autoplay policy, which was a software update that caused issues for web apps, games, and interactive art by preventing them from playing audio as intended [71223]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident described in the article is non-malicious. Google partially rolled back Chrome's blocking of autoplaying video with sound after it was found to break a large collection of web apps and games. The update broke apps, games, and interactive art, preventing them from playing audio for alerts and other elements, causing complaints from developers and users. The rollback was aimed at giving developers more time to update their code before the policy is reapplied in Chrome 70 [Article 71223]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The intent of the software failure incident related to poor decisions can be inferred from the article. Google's decision to roll out the autoplay blocking feature in Chrome, which ended up breaking a series of apps, games, and interactive art due to the removal of audio elements, can be seen as a poor decision. This decision led to complaints from developers and users, highlighting the negative impact it had on various web applications [71223]. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident in the article can be attributed to development incompetence. The blocking feature introduced in Chrome to prevent autoplaying videos with sound ended up breaking a series of apps, games, and interactive art, preventing them from playing audio for alerts and other elements. This issue arose because the update did not consider the impact on these interactive web apps, leading to complaints from developers and users [71223]. The decision to temporarily remove the autoplay policy for the Web Audio API in Chrome 66 and delay its reapplication until Chrome 70 was met with skepticism by developers, highlighting a lack of foresight in the initial implementation of the feature [71223]. |
| Duration |
temporary |
The software failure incident described in the article is temporary. Google partially rolled back Chrome's blocking of autoplaying video with sound after it was found to break a large collection of web apps and games. The update broke a series of apps, games, and interactive art, preventing them from playing audio for alerts and other elements. Google updated Chrome 66 to temporarily remove the autoplay policy for the Web Audio API to give developers more time to update their code. The policy will be reapplied in Chrome 70 in October [Article 71223]. |
| Behaviour |
omission, other |
(a) crash: The software failure incident in the article does not involve a crash where the system loses state and does not perform any of its intended functions. The issue with Chrome's blocking of autoplaying videos with sound did not result in a complete system failure but rather a specific functionality issue affecting web apps and games [Article 71223].
(b) omission: The software failure incident can be categorized under omission, as the update in Chrome's autoplay policy omitted to perform its intended functions correctly for a series of apps, games, and interactive art. This omission led to the prevention of these applications from playing audio for alerts and other elements, causing complaints from developers and users [Article 71223].
(c) timing: The software failure incident is not related to timing, where the system performs its intended functions but too late or too early. The issue with Chrome's autoplay policy did not involve a timing-related failure but rather a functionality issue affecting the audio playback of web apps and games [Article 71223].
(d) value: The software failure incident does not fall under the category of a value-related failure, where the system performs its intended functions incorrectly. The issue with Chrome's autoplay policy did not involve incorrect performance but rather a specific functionality issue related to audio playback for certain applications [Article 71223].
(e) byzantine: The software failure incident is not characterized by a byzantine behavior, where the system behaves erroneously with inconsistent responses and interactions. The issue with Chrome's autoplay policy did not involve inconsistent responses but rather a specific functionality issue affecting audio playback for certain web apps and games [Article 71223].
(f) other: The software failure incident can be categorized as a specific functionality issue that arose due to the change in Chrome's autoplay policy. This behavior can be classified as a functional failure where the system did not perform a specific function related to audio playback correctly for certain applications [Article 71223]. |