Skip to content
This repository has been archived by the owner on Jan 10, 2019. It is now read-only.

Wrong parse content from Mozilla Developer Network #9

Open
boozook opened this issue Mar 20, 2016 · 5 comments
Open

Wrong parse content from Mozilla Developer Network #9

boozook opened this issue Mar 20, 2016 · 5 comments

Comments

@boozook
Copy link

boozook commented Mar 20, 2016

EXAMPLE, see screenshot:

<pre><code>window.alert(message);</code></pre>« Window

screen shot 2016-03-20 at 20 43 58

@Derron15
Copy link

What is needed to be changed?

@boozook
Copy link
Author

boozook commented Apr 27, 2016

Need to remove <pre><code> from text and its content wrap into real node code.

@mrshu
Copy link
Contributor

mrshu commented Apr 27, 2016

@Derron15 @fzzr- is right. I would like to note that we are deprecating this feature (Instant Answers in Google/Bing) because it brings a lot of problems and not too much value.

The removal of this feature will happen very soon so I do not think it would be wise to spend your time fixing it.

@boozook
Copy link
Author

boozook commented Apr 27, 2016

@mrshu, what will instead?

@mrshu
Copy link
Contributor

mrshu commented Apr 27, 2016

@fzzr- I am not sure what you mean but the general plan is to support those parts of the extensions that are used and bring some value. Answers in Google/Bing failed to meet this criteria in both cases -- this bug is just the tip of the iceberg.

That being said, the extensions are open source! The beauty of it is that you can easily maintain a fork of the extension for your own use. Given that the extensions use git for version control, this should be very easy, you can just merge commits from the upstream (master on this repository).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants