Closed Bug 710148 Opened 14 years ago Closed 14 years ago

Remove MOZ_REQUIRE_CURRENT_SDK from nsPrintDialogUtil.cpp

Categories

(Core Graveyard :: Embedding: GRE Core, defect)

All
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla11

People

(Reporter: m_kato, Assigned: emorley)

References

()

Details

Attachments

(1 file)

MOZ_REQUIRE_CURRENT_SDK is unused. We should remove MOZ_REQUIRE_CURRENT_SDK related code in embedding/components/printingui/src/win/nsPrintDialogUtil.cpp. MOZ_REQUIRE_CURRENT_SDK is used on Firefox 1?, but Gecko 1.8 and later, this isn't used.
Assignee: nobody → bmo
Status: NEW → ASSIGNED
Attachment #581582 - Flags: review?(benjamin) → review+
Flags: in-testsuite-
Target Milestone: --- → mozilla11
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Was this change in the right direction? It looks like we now (compile-time) unconditionally use the *old* print dialog rather than the *new* one.
MOZ_REQUIRE_CURRENT_SDK wasn't defined anywhere, so the removed code shouldn't have been being compiled anyway, unless I'm missing something? http://mxr.mozilla.org/mozilla-central/search?string=MOZ_REQUIRE_CURRENT_SDK I'm afk until Monday, but if this was indeed the wrong way, please do back me out! :-)
Sorry, I should have been clearer. I'm aware it wasn't being compiled. I'm asking whether it *should* have been compiled (possibly under some other conditional - looking at widget/src/windows, we seem to be using '#if MOZ_WINSDK_TARGETVER >= something' for similar scenarios).
(In reply to Zack Weinberg (:zwol) from comment #7) > Sorry, I should have been clearer. I'm aware it wasn't being compiled. I'm > asking whether it *should* have been compiled (possibly under some other > conditional - looking at widget/src/windows, we seem to be using '#if > MOZ_WINSDK_TARGETVER >= something' for similar scenarios). Actually, this code is broken and cannot compile due to various compile error now. We should re-design print dialog if UX team is needed.
(In reply to Makoto Kato from comment #8) > > Actually, this code is broken and cannot compile due to various compile > error now. > > We should re-design print dialog if UX team is needed. Thanks for the update. In that case, I am happy with what was done here; future adjustments can happen in bug 693230 and/or bug 650957.
Phew! Had me worried there for a sec! Second pair of eyes always appreciated though, so thanks for checking :-)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: