Multiverse Feedback: Recent Activity
| Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics | Upcoming releases | Skeleton |
Recent updates to Multiverse Feedback: (Generated at 2025-09-03 09:04:06)
looks like I fixed this at some point
fixed, basically
Right. This is mostly fixed. The error on clicking "printable" is fixed. The VS colourlessness is fixable in Firefox and IE - you just have to hunt the "Print background colours and images" option.
Chrome, astonishingly, don't give this option to the user. They leave it entirely at the webmaster's discretion which backgrounds should be printable. I've added the obscure proprietary CSS tag to make the colouring work in Chrome, but it seems this feature is very new and rough in Chrome (it only works at all in Chrome 17+); in particular, gradient backgrounds go horribly wrong. For the moment I've disabled any attempts to print gradients in Chrome, which means multicolour and artifact cards look less nice, and hybrid cards just come out horrible.
I'm left with no choice but to recommend against printing Multiverse cards from Chrome for the moment. Use IE or Firefox instead :/
Further reading: how to enable printing backgrounds in assorted browsers, the bug report I submitted to Chrome for the gradients issue
Seems a reasonable suggestion, especially for community cardsets like the design challenge and the community set. I'll see what I can do.
Darn, my apologies - that's a silly bug I introduced trying to make printable mode omit as much as possible. It omits slightly too much. I'll get that fixed ASAP (hopefully tonight).
As for the VS colourlessness when printing, yeah, looks like I can reproduce that too. It seems like a CSS media issue, but I'm not using CSS media restrictions. I'll investigate.
Once Alex creates My Cards , that will become much easier.
Oh, also, I've tried to just print the cards straight up from the visual spoiler, but for some strange reason the frames don't print in color, just the expansion symbols. I can't figure out if this is a you problem, or a me problem, so I'm throwing that out there.
Hah, and mtgo doesn't need them; as it could easily fan out just the cards in graveyard that matter; and your opponent can't watch you looking.
What's strange is that they still use them on MTGO (for new cards), acknowledging that they are in fact useful.
I always found it to be an appealing little graphic icon too, though it doesn't quite mesh with the modern frame.
Back in the day, I did find them faintly useful. I was sad when Wizards said they wouldn't be happening on cards after Odyssey block.
I'm not going to argue whether they should exist or not. I'm just wondering how useful people found them when they existed. I mean, the whole point was so that you could easily spot the gravestone symbol in your graveyard, when your cards were fanned, and, therefore, know that you had effects down there. Did that work with people? Did anyone scan for the graveyard symbol over looking at individual cards?
Color indicators do in fact have rules meaning: on a card like Karoo Myr Cat, the lack of an indicator means it would need an extra ability to say that it's white.
Graveyard icons, on the other hand, are officially meaningless, and they aren't used with the modern card frame at all, even for reprints of cards that originally had the graveyard icon (the Commander version of Wonder, or the upcoming reprint of Ray of Revelation in Dark Ascension).
Hmm. So it is.
Still a problem
Um, nope. Now my cards are cut in half. For example: Bad Wolf Entity.
fixed, more or less
I should also provide the ability to mass-assign active status of true or false. noyahuid encountered this here.
Oh. Hmm. That's not a bad idea. I might see if I can work that in, even if just for tooltips.
Oh, I meant keep the tooltip the same size; but always force the card image to be scaled.
Hah. It ain't an img. Not at the time my AJAX library looks for it. It's just an
<a>with a class or two. It only finds out it's an img when the request comes back from the server, which is long after the Prototip library has locked in the width that the tooltip will be henceforth & forever.But it's okay, as I said over on Haunting Vision, I do have a fix already working locally; when generating the
<a>I look at what the card is at that point, and add a class to the link that my client-side JS uses to take a reasonable guess as to how big to make the tooltip.If you do you'll make friends, the web guy here is fuming at the lack of decent working tooltip libraries anywhere on the net. (As an immediate fix - set the width and height attributes on the img?)
done!
done!
done!
done!
done!