Chrome 130.0 ‑ Acceptance | destinations: a child region’s ancestor is named and region sorting includes that
Chrome 130.0 ‑ Acceptance | destinations: a destination can be created and will appear at the top of the list
Chrome 130.0 ‑ Acceptance | destinations: a destination can be deleted
Chrome 130.0 ‑ Acceptance | destinations: a destination can be edited and edits can be cancelled
Chrome 130.0 ‑ Acceptance | destinations: a new destination defaults to the same region as the previously-created one
Chrome 130.0 ‑ Acceptance | destinations: a region can be entered and destinations will be scoped to it
Chrome 130.0 ‑ Acceptance | destinations: destination status doesn’t show when the feature flag is off
Chrome 130.0 ‑ Acceptance | destinations: destination status is displayed and can be toggled from the list when the feature flag is on
Chrome 130.0 ‑ Acceptance | destinations: existing destinations are listed and can be sorted by region or awesomeness
Chrome 130.0 ‑ Acceptance | destinations: persisted sort is restored
Chrome 130.0 ‑ Acceptance | destinations: the destination’s suggested mask is based on the adventure
Chrome 130.0 ‑ Acceptance | destinations: the status fieldset doesn’t show when the feature isn’t on
Chrome 130.0 ‑ Acceptance | destinations: unmnemonic devices suggests and requires a mask
Chrome 130.0 ‑ Acceptance | regions with existing map: an existing map is displayed and can be updated
Chrome 130.0 ‑ Acceptance | regions with no map: a new map can be uploaded
Chrome 130.0 ‑ Acceptance | regions: a region can be created, will appear in alphabetic order, and be the default for a new destination
Chrome 130.0 ‑ Acceptance | regions: a region can be deleted
Chrome 130.0 ‑ Acceptance | regions: a region can be edited and edits can be cancelled
Chrome 130.0 ‑ Acceptance | regions: an edited region is the default for a new destination
Chrome 130.0 ‑ Acceptance | regions: existing regions are listed
Chrome 130.0 ‑ Acceptance | regions: regions have a completion status for txtbeyond
Chrome 130.0 ‑ Acceptance | regions: the regions can be arranged on a map
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: a destination with a meeting is indicated
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: a new meeting can be scheduled and resets the form when saved
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: a newly created and available destination will show under its region
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: a partially-complete meeting can be cleared
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: an existing meeting can be edited
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: an existing meeting is shown in the teams and destination
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: available destinations are grouped by nested regions
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: choosing teams causes destinations outside their risk to be faded as ineligible
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: hovering over a team shows its destinations ordered on the map, its meetings, and teams it’s met
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: meeting components can be unselected
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: regions with available destinations are displayed on the map and highlight when hovered in the column
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: scheduling a meeting between teams with different meeting counts is impossible
Chrome 130.0 ‑ Acceptance | scheduler > for Clandestine Rendezvous: teams are listed
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: a nested region does not show on the map
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: a new meeting can be scheduled and resets the form when saved
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: an existing meeting can be edited
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: an existing meeting is shown in the teams and destination
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: available waypoints are grouped by nested regions
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: hovering over a team shows its destinations and waypoints ordered on the map, its meetings, and teams it’s met
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: meeting components can be unselected
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: selecting a second team for a meeting does nothing
Chrome 130.0 ‑ Acceptance | scheduler > for unmnemonic devices: the offset field is hidden
Chrome 130.0 ‑ Acceptance | settings: existing: an existing settings document is displayed and can be updated, with its boolean flags mirrored to the features service
Chrome 130.0 ‑ Acceptance | settings: fresh: a new settings document can be created and saved
Chrome 130.0 ‑ Acceptance | sync: can sync with another database, syncs are remembered and can be returned to and removed
Chrome 130.0 ‑ Acceptance | teams: existing teams are listed
Chrome 130.0 ‑ Acceptance | teams: teams can be added and updated with JSON input
Chrome 130.0 ‑ Acceptance | teams: teams can have identifiers for unmnemonic devices
Chrome 130.0 ‑ Acceptance | waypoints: a new waypoint defaults to the same region as the previously-created one
Chrome 130.0 ‑ Acceptance | waypoints: a region can be entered and waypoints will be scoped to it
Chrome 130.0 ‑ Acceptance | waypoints: a waypoint can be created and will appear at the top of the list
Chrome 130.0 ‑ Acceptance | waypoints: a waypoint can be edited and edits can be cancelled
Chrome 130.0 ‑ Acceptance | waypoints: existing waypoints are listed
Chrome 130.0 ‑ Acceptance | waypoints: persisted sort is restored
Chrome 130.0 ‑ Acceptance | waypoints: the status fieldset doesn’t show when the feature isn’t on
Chrome 130.0 ‑ Acceptance | waypoints: validation errors show on the form
Chrome 130.0 ‑ Acceptance | waypoints: waypoint status doesn’t show when the feature flag is off
Chrome 130.0 ‑ Acceptance | waypoints: waypoint status is displayed and can be toggled from the list when the feature flag is on
Chrome 130.0 ‑ Acceptance | waypoints: waypoints do not show otherwise
Chrome 130.0 ‑ Acceptance | waypoints: waypoints show for unmnemonic devices
Chrome 130.0 ‑ Integration | Modifier | draggable-number: it lets number fields be set by dragging
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | chooseBlankIndex: it chooses a blank index
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | chooseBlankIndex: throws if the answer and mask have a mismatch
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | maskIsValid: it checks mask validity
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | suggestedMask: it suggests masks
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | teamDigitsForAnswerAndGoalDigits: assigns the entire difference to the team if there is only one
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | teamDigitsForAnswerAndGoalDigits: splits the difference between teams
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | teamDigitsForAnswerAndGoalDigits: throws if there are more than two teams
Chrome 130.0 ‑ Unit | Service | Clandestine Rendezvous | teamDigitsForAnswerAndGoalDigits: throws if there no teams
Chrome 130.0 ‑ Unit | Service | txtbeyond: it checks description validity
Chrome 130.0 ‑ Unit | Service | txtbeyond: it checks mask validity
Chrome 130.0 ‑ Unit | Service | txtbeyond: it converts team names into Twitter usernames
Chrome 130.0 ‑ Unit | Service | txtbeyond: it extracts masks from descriptions
Chrome 130.0 ‑ Unit | Service | txtbeyond: it removes masks from descriptions
Chrome 130.0 ‑ Unit | Service | txtbeyond: it suggests masks
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices | dimensionsIsValid: it checks dimensions validity
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices | excerptIsValid: it checks excerpt validity
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices | outlineIsValid: it checks outline validity
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices | parsedDimensions: it parses dimensions
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices | parsedOutline: it parses outlines
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices: it accepts all descriptions
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices: it extracts answers
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices: it suggests masks
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices: postExcerpt returns the text before the excerpt
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices: preExcerpt returns the text before the excerpt
Chrome 130.0 ‑ Unit | Service | unmnemonic-devices: trimmedInnerExcerpt returns the text inside the excerpt without punctuation
Chrome 130.0 ‑ ember-qunit: Ember.onerror validation: Ember.onerror is functioning properly
Chrome 130.0 ‑ service:pathfinder: it finds distances
Chrome 130.0 ‑ service:pathfinder: it knows whether it contains a region