Dungeon map stays small in the middle after going from the quest log (L) to the maximized map (M) inside a dungeon

Open Beginner friendly
#297 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@gOOvER is already working on this.

Since Nov 17, 2026.

  • #322 by @gOOvER — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
lua
Domain
frontend

Research direction

Start with Map/Window.lua, especially FillScreen around lines 79–87, then follow Refit() to ScrollContainer:OnCanvasSizeChanged. Check how maximizing or minimizing and showing or hiding the quest log updates the Blizzard dungeon map canvas. Done means the map art fills the maximized window after the described L-to-M sequence; verify behavior without affecting the stitched world map.

Written by the indexing model from the issue text.

Description

Steps

  1. Inside a dungeon, press L (quest log, windowed map).
  2. Press M (maximized map).
    The dungeon map art keeps the small window's size and sits in the middle of the big window.
    Closing and reopening the map shows it at the right size.

It is Blizzard's own map for that dungeon, not the stitched world map.

Cause (read from the code, not confirmed in game)
Map/Window.lua FillScreen (lines 79-87) calls Refit() only when it actually changes the
frame width:

  if math.abs(map:GetWidth() - w) < 1 then return end
  map:SetWidth(w)
  Refit()

When the width is already the full width, Refit (ScrollContainer:OnCanvasSizeChanged)
is not called, so the canvas keeps the old fit.

Workaround I use
Calling WorldMapFrame.ScrollContainer:OnCanvasSizeChanged() after Maximize/Minimize and
after the quest log shows/hides, when the map is not the stitched one.

Environment

  • WoW Forever (Interface 16001), Korean client (koKR)
  • OpenMap v0.8.9
  • Other addons: Attune, Auctionator, ForeverDungeonJournal, ForeverPowerBars, RogueEnergyCombo
  • Tested with OpenMap disabled: the message in issue 1 stopped appearing (short test, a few minutes)
Dominant language
Lua
Stars
20
Forks
6
Avg merge
23h 27m
Merged PRs (30d)
45

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 openmap-world/openmap

All issues in openmap-world/openmap

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.