# Feature COMMS-649 - Continue working on documents while offline

Project: Stream Communicator
Status: in development
URL: https://community.openproject.org/work_packages/COMMS-649

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.1.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | RM Document collaboration |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| COMMS-659 | Remove test-mode for local document fallback, require Hocuspocus provider | Implementation | closed |  | 17.4.0 |  |
| COMMS-660 | Implement UI/UX for new connection error/restore banner  | Implementation | closed |  | 17.4.0 |  |

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Documents |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/d3zhm0R0pjHJvQd3XTlxuS/New-Documents-module?node-id=2816-7124&t=rka49PeV7ri5adQ8-4 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Kabiru Mwenja |
| Accountable |  |
| Product manager |  |
| Developers | Ihor Dubas, Kabiru Mwenja |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an editor of a document  
**I want to** be able to read and write documents even when my network is flaky  
**so that** I am not kicked out of the flow of writing

**Acceptance criteria**

  - If the network drops after I initially loaded a document I can continue writing to the document

  - Once the network is back those edits get synced and persisted on the server.

  - When the page goes offline, there are a number of indications that I'm in offline mode:
    
      - Show an warning hint in the header "Currently offline"
    
      - The information on active users is gone
    
      - The information of the last successful save is gone

  - When the connection is restored:
    
      - For the duration of 5 seconds:
        
          - Turn the hint in the header into a success message "Connection reestablished":
        
          - The information on active users is still gone
        
          - The information of the last successful save is still gone
    
      - After 5 seconds:
        
          - Remove the green success hint "Connection reestablished"
        
          - Show the header the same as before the connection loss.

**Technical notes**

  - Hopefully that is as easy as adding a y-indexeddb provider. 🤞 

**Permissions and visibility considerations**

  - When user only has read permissions, the user should continue having read-only permissions when offline.

**Out of scope**

  - Syncing of the documents when the document is not open

  - Moving the position of the banner to the bottom right; this will be handled in a separate feature: <mention class="mention" data-id="72657" data-type="work_package" data-text="##72657">\#\#72657</mention>