bluegriffon export inline styles to external css

BLUEGRIFFON EXPORT INLINE STYLES TO EXTERNAL CSS PATCH
BLUEGRIFFON EXPORT INLINE STYLES TO EXTERNAL CSS CODE

I haven't spent more than a few minutes looking at how much I have to work with, so I'm not sure of the best way to go about doing that. Currently, wbp fixes up persisted files with nsIChannel-derived mime types since we're not downloading the CSS files we persist from a remote server, that's not going to work. Right now, the biggest thing left to implement feature-wise is to make CSS and other content-serialized, not-downloaded files get the right file extension. I've tried to avoid gratuitous refactoring of nsWebBrowserPersist, opting for small changes/hacks around an architecture not really aligned with the sequence of operations CSS serialization requires. I'm leaving for the rest of the weekend in half an hour to run my first half marathon (eep!) so I figured I'd post what I have so far for preliminary review. Splinter Review So I've been working on dbaron's suggestion for a week or two now. Preliminary, incomplete implementation (obsolete) I think this is highly preferable to reimplementing CSS parsing and serialization. This object would further have to be passed down through nsCSSDeclaration::ToString and the methods it calls - where, again, null would mean that no fixup was needed. Furthermore, we would then add Serialize methods to everything that has a GetCssText method by renaming GetCssText and adding the argument to this new interface - and then adding a GetCssText that called Serilaize(null) - where the null object for this new interface would mean to do no URI fixup. Then we could add a Serialize method to nsIStyleSheet that took one of these as an argument (but where the object being null would mean no URI fixup was needed). In other words, the interface would take a URI as input (probably nsIURI) and return a URI as output (probably string), potentially enqueueing the saving of the URI in question as part of the implementation.

BLUEGRIFFON EXPORT INLINE STYLES TO EXTERNAL CSS CODE

To avoid having two separate bits of CSS serialization code, we should teach the style system to serialize with URI fixup.įor a start, this requires the nsWebBrowserPersist code to implement an interface a lot like nsIDocumentEncoderNodeFixup - except for URI fixup. So, for what it's worth, the way I think this ought to be fixed is roughly as follows: Image is dark, but the background-color isn't set) (same issue when browsing some sites while theīrowser is set w/images off: eg if the font color is white & the background Impossible without editing the HTML/CSS, if the page is written with the font &īackground colour the same. This is not not critical, but may render off-line viewing of saved webpages

hover mouse over desired CSS background imageĢ. Saved all images, even thoses declaired in CSSġ. Menu:File/Save As./Save As Type: Web Page, complete (sorry, searched but couldn't find this reportĢ. > *** Bug 245799 has been marked as a duplicate of this bug.

BLUEGRIFFON EXPORT INLINE STYLES TO EXTERNAL CSS PATCH

For example:įinally, the patch will have to be able to extract and fixup multiple urls that Nasty extra styles to leap into existence. style property on an element results in all kinds of I'll have to figure out how it is getting its base address and fix it.Ģ. Url into an absolute URL using the base address of the original location. The call to cssDeclOut->SetProperty(propName, newValue, propPriority) duringįixup results in a mutant URL caused by the CSS resolving the supplied relative Skips quoted text in values, fixes the broken comment, removes actually fixes up content now, but is busted in a couple of ways:ġ. NS_ARRAY_LENGTH, adds support for various 'cursor-*' props but not 'content', Splinter Review Patch addresses most of the issues but is still work in progress.

Bluegriffon export inline styles to external css