[18.0][BUG] web_chatter_position pdf preview glitch on sided mode

Open
#3,109 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by reading the web_chatter_position addon and tracing how PDF attachments are opened in sided chatter mode; the issue gives runbot reproduction steps but names no source files or tests. Reproduce on version 18.0, then compare with version 17.0. Done means clicking an attached PDF displays it in the right sided chatter panel as expected.

Written by the indexing model from the issue text.

Description

bug

Module

web_chatter_position

Describe the bug

On version 18.0 there is a glitch rendering when previewing a pdf in the sided/responsive mode for the chatter.

In version 17.0 it was displaying the pdf in the chatter on sided mode.
In version 18.0 the pdf is displayed in a pop up window which is the same behaviour that the below mode for the chatter on version 17.0

To Reproduce

Affected versions: 18.0

Steps to reproduce the behavior:

  1. on runbot, on the web repository
  2. in the user preference set the chatter position to sided
  3. open a form on any model with chatter on it (sale.order, account.move,...)
  4. in the chatter attach a pdf to the record
  5. if the attachment panel is not displayed click on the paperclip icon
  6. move the mouse cursor to the pdf document
  7. the cursor show up as a magnifying glass
  8. click on the pdf
  9. the pdf open in a popup window.

Expected behavior
Having the pdf showing up in the right sided panel (the chatter panel in sided mode) as it does for the version 17.0

Dominant language
JavaScript
Stars
1.2k
Forks
2.2k
Avg merge
3d 15h
Merged PRs (30d)
30

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OCA/web

All issues in OCA/web

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.