Files

gsinghpal 082c585e24 fix(shopfloor): mobile scroll works — remove nested scroll containers

User: "scrolling is not working" in Chrome DevTools mobile simulation.
Three actual problems:

1. Plant Overview columns had max-height: calc(100vh - 180px) +
   overflow: hidden, with a nested overflow-y: auto on the column
   body. Classic Trello kanban pattern — works on desktop, breaks
   on mobile. You get two scroll containers fighting each other and
   the PAGE itself can't scroll past the viewport height.

2. .o_fp_po_columns had overflow-x: auto on all widths. On the
   phone-stack breakpoint (<600px) this was also still on, creating
   another nested scroll container.

3. Draggable cards can swallow touch events on mobile because
   touch-action defaults to "auto" and Chrome's mobile simulator
   treats touch on draggable elements as potential drag-start.

Fixes — all at the <=900px breakpoint (tablets + phones):

  .o_fp_po_column          max-height: none; overflow: visible
  .o_fp_po_col_body        overflow-y: visible
  .o_fp_po_columns         flex-direction: column; overflow: visible

Plus .o_fp_po_card carries `touch-action: pan-y` unconditionally —
touch-scroll gestures never get hijacked by the draggable="true"
attribute. Desktop mousedown drag still works (HTML5 drag-drop
isn't touch-based by default).

Also added -webkit-overflow-scrolling: touch to all three page
roots (.o_fp_tablet, .o_fp_manager, .o_fp_plant_overview) and to
the internal scroll containers that remain on desktop — gives iOS
Safari proper momentum scroll (11 occurrences in the compiled
bundle).

Drag-drop JS preventDefault calls audited — they only fire on
dragover/drop (HTML5 drag events), which don't exist on touch by
default, so no touch interference there.

Verified via compiled CSS:
  .o_fp_po_card { touch-action: pan-y; ... }
  @media (max-width: 900px) .o_fp_po_column { overflow-x: visible;
         overflow-y: visible; min-height: auto }
  @media (max-width: 900px) .o_fp_po_col_body { overflow-y: visible }

Version bumped 19.0.5.0.0 -> 19.0.6.0.0 to force the bundle hash
to change. New URL: /web/assets/4a1b69e/web.assets_backend.min.css

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-18 19:40:52 -04:00

controllers

fix(manager-desk): unstick the spinner + live updates that don't flash

2026-04-18 18:06:04 -04:00

data

folder rename

2026-04-16 20:53:53 -04:00

models

folder rename

2026-04-16 20:53:53 -04:00

security

folder rename

2026-04-16 20:53:53 -04:00

static/src

fix(shopfloor): mobile scroll works — remove nested scroll containers

2026-04-18 19:40:52 -04:00

views

feat(shopfloor): Manager Desk — assign workers, swap tanks, take over (CHUNK 2/4)

2026-04-17 20:03:01 -04:00

__init__.py

folder rename

2026-04-16 20:53:53 -04:00

__manifest__.py

fix(shopfloor): mobile scroll works — remove nested scroll containers

2026-04-18 19:40:52 -04:00

README.md

folder rename

2026-04-16 20:53:53 -04:00

README.md

Fusion Plating — Shop Floor

Tablet / operator ergonomics layer for the fusion_plating core.

What this module adds

Feature	Model
Tablet station registration	`fusion.plating.shopfloor.station`
Bake oven master + chart recorder ref	`fusion.plating.bake.oven`
Hydrogen embrittlement bake-window enforcer	`fusion.plating.bake.window`
First-piece inspection gate	`fusion.plating.first.piece.gate`
Operator next-up queue (transient)	`fusion.plating.operator.queue`

Bake-window enforcer

When a high-strength-steel part exits the plating tank, a clock starts. Customer specification dictates the window (typically 1-4 hours) inside which the relief bake must begin. Missing the window requires scrap or rework — there is no retroactive fix.

The module models this as a first-class entity with:

plate_exit_time — clock start
window_hours — customer spec
bake_required_by — computed deadline
state — awaiting_bake -> bake_in_progress -> baked, with missed_window / scrapped exit paths
A 5-minute cron that flips records past their deadline to missed_window automatically
A kanban board grouped by state with theme-aware status colours

Tablet client

A backend OWL component (Odoo 19 conventions) registered as the fp_shopfloor_tablet client action. It hosts:

QR scan input (wedge scanner or on-screen keyboard friendly)
Live tank / bath / job preview cards
One-tap Start Bake / End Bake buttons
Live operator next-up queue

JSON-RPC endpoints (Odoo 19 type='jsonrpc'):

POST /fp/shopfloor/scan
POST /fp/shopfloor/log_chemistry
POST /fp/shopfloor/start_bake
POST /fp/shopfloor/end_bake
POST /fp/shopfloor/queue

QR code conventions

Prefix	Resolves to
`FP-TANK:<code>`	`fusion.plating.tank`
`FP-BATH:<name>`	`fusion.plating.bath`
`FP-STATION:<code>`	`fusion.plating.shopfloor.station`
`FP-JOB:<name>`	`fusion.plating.bake.window`
`FP-OVEN:<code>`	`fusion.plating.bake.oven`

Security

Reuses the four core Fusion Plating groups (operator, supervisor, manager, admin) defined in fusion_plating. No new groups, no new privilege block. ACLs are graded operator (read/write logs), supervisor (create), manager (full).

Theme

All styling is theme-aware: CSS custom properties + color-mix() against Bootstrap / Odoo tokens. No hex codes, no media queries — works in light and dark mode out of the box.

Install / update

docker exec odoo-dev-app odoo -d fusion-dev -u fusion_plating_shopfloor --stop-after-init