WO2013159745A1 - 网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 - Google Patents
网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 Download PDFInfo
- Publication number
- WO2013159745A1 WO2013159745A1 PCT/CN2013/074887 CN2013074887W WO2013159745A1 WO 2013159745 A1 WO2013159745 A1 WO 2013159745A1 CN 2013074887 W CN2013074887 W CN 2013074887W WO 2013159745 A1 WO2013159745 A1 WO 2013159745A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- page
- application
- webapp
- browser
- read
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
Definitions
- Web browsing method WebApp framework, execution JavaScript method and device, mobile terminal
- the present invention relates to the field of mobile communications, and more particularly to a web browsing method implemented based on a WebApp framework, a WebApp framework, a method and apparatus for executing JavaScript using an extended interface, and the above-described WebApp framework or the above-described mobile terminal executing a JavaScript device.
- Background technique
- multiple mobile browsers such as QQ browser, beautiful browser, and UC browser, will display customized forums for various forums, that is, custom forum mode.
- the implementation of the forum mode mainly adopts the following two methods: 1. Relying on the browser manufacturer's own server implementation. 2. Implemented on a local browser client.
- Reading mode can transform the deep and shallow texts of novels, news, forums, etc. from a thick book into a thin one. Paper. Just one page, just look at the whole, let the palm reading really become the user's love. In operation, this change makes browsing easier and speeds up reading. However, they both directly modify the browser source code and add the implementation logic of the reading mode in the browser to implement the reading mode. However, there are many drawbacks to this approach:
- the typesetting method of the mobile phone browser generally has two modes of adapting to screen typesetting and zooming typesetting. These two methods have their own advantages and disadvantages: adapt to screen layout without left and right drag, or page zoom, so it is more suitable for mobile phone browsing experience, but the layout of the page is sometimes confusing and unattractive; zoom typesetting can completely restore PC-like The page effect, the page is beautiful and there is no confusion, but the user needs to constantly drag or zoom, which reduces the user's browsing experience.
- Some mobile browsers are now starting to support extensions to enhance the user's browsing experience. For example, forum mode, microblogging reading mode, etc., to enhance the user's browsing experience in the mobile browser.
- the extension of the mobile browser is to provide more and better experience, and the browser must provide more and better open interfaces.
- Extensions change the DOM (Document Object) via JavaScript (hereafter referred to as JS)
- JS JavaScript
- the structure of the Model, Document Object Model implements the re-formatting of the page, making the page more beautiful. For example, blocking unnecessary ad nodes; extracting the necessary elements from the forum page to form a forum mode suitable for mobile browsing.
- Another object of the present invention is to provide a method and apparatus for executing JavaScript using an extended interface. Another object of the present invention is to provide a web browsing method and a web App framework based on a WebApp framework.
- a method for executing extended JavaScript by an extended JS interface comprising: when a webpage page is loaded, asking a requester to execute extended JavaScript at a predetermined timing, wherein the extension is Loaded when the browser is launched; when it is determined that JavaScript is required to execute the extension, the browser assembles the extended JS interface according to the open API; and executes the extended JavaScript using the extended JS interface.
- the extended JavaScript is executed to perform the following steps: by accessing a DOM tree of a current webpage page, extracting a page browsing desired content; according to the extracted content, by setting in advance
- the interface for adjusting the layout mode sets the layout mode of the browser; based on the set layout mode, performs page layout on the extracted content.
- the extended JavaScript is executed to perform the following steps: after receiving an instruction issued by the browser to invoke a first message pre-registered in the first JS application in the web application WebApp framework
- the WebApp invokes the first JS application to determine whether the current webpage page is a customizable forum page, and the first JS application is set to be a forum type that is called after the HEAD node is constructed and used to determine the current webpage page.
- a message is sent after completing the construction of the HEAD node of the current web page when loading the webpage to the browser; determining that the current webpage page is a customizable forum page and receiving an instruction issued by the browser to invoke the pre-registration in the WebApp framework
- the WebApp calls the forum with the current web page a second JS application corresponding to the type to generate and display the customized forum page, the second JS application being set to be called after the document object model DOM tree construction is completed and used to generate and display the forum page, the second The message is sent after the DOM tree of the current web page is completed when the web page is loaded into the browser.
- the extended JavaScript is executed to perform the following steps: After receiving an instruction issued by the browser to invoke a fourth message of a fourth JS application pre-registered in the WebApp framework, the WebApp Calling the fourth JS application to perform the following steps: traversing the DOM tree to obtain keywords contained in the DOM node text; determining the keyword based on keywords included in the DOM node text and a pre-stored keyword database in the WebApp framework Whether it is a pre-read keyword; after determining that the included keyword is a pre-read keyword, the following process is repeated for each pre-read keyword until all the pre-read keywords have been processed: according to the currently acquired Pre-reading the keyword, obtaining the link address of the page of the next page; pre-reading the content of the next page from the web server according to the obtained link address; and displaying the content of the next page of the pre-read and obtaining the next pre-read keyword, wherein The fourth message is sent after completing the construction of the DOM tree of the current webpage
- a webpage browsing method based on a WebApp framework including: after receiving an instruction issued by a browser to invoke a first message of a first JS application pre-registered in a web application webApp framework, The WebApp invokes the first JS application to determine whether the current webpage page is a customizable forum page, and the first JS application is set to be a forum type that is called after the HEAD node is constructed and used to determine the current webpage page, the first The message is sent after completing the construction of the HEAD node of the current webpage page when the webpage is loaded to the browser; determining that the current webpage page is a customizable forum page and receiving an instruction issued by the browser invokes a second pre-registered in the WebApp framework.
- the WebApp invokes a second JS application corresponding to the forum type of the current web page to generate and display the customized forum page, and the second JS application is set to be completed in the DOM tree of the document object model.
- the second message is in the browser Issued after the completion of construction of the current DOM tree of the web page upload page.
- the first JS application and the second JS application may be The content script Content Script is formed and pre-programmed in the WebApp installation package, and when the WebApp installation package is installed on the browser, the first and second JS applications are registered in the WebApp framework.
- the first JS application is configured to: obtain a meta tag from the HEAD node; determine a forum type of the web page according to the acquired meta tag, and the second JS application The method is configured to: extract the forum page data corresponding to the customized forum mode in the current webpage page by traversing the DOM tree; generate the forum page by using the extracted forum page data; and display the generated forum page.
- the method prior to displaying the generated forum page, the method further includes hiding or deleting the original JS page.
- the method further includes: after receiving the instruction issued by the browser to invoke a third message of the third JS application pre-registered in the WebApp framework, the WebApp invokes the third JS application.
- the determination of the pre-read keyword and the web content pre-reading and display process based on the determined pre-read keyword are performed.
- the determining of the pre-read keyword and the web content pre-reading and displaying process based on the determined pre-reading keyword include: traversing the DOM tree to obtain keywords included in the DOM node text; based on the DOM node The keyword contained in the text and the pre-read keyword pre-stored in the WebApp framework to determine whether the keyword is a pre-read keyword; after determining that the included keyword is a pre-read keyword, for each pre-read The read keyword repeatedly performs the following process until all the pre-read keywords have been processed: According to the currently acquired pre-read keywords, the link address of the next page page is obtained; according to the obtained link address, the pre-read from the web server The next page webpage content; and displaying the pre-read next page webpage content and obtaining the next pre-reading keyword, wherein the third message is sent after completing the construction of the DOM tree of the current webpage page, and the third JS application is Set to be called after the DOM tree is built and formed by Content Script, and pre-programmed in the Web
- the method before displaying the pre-read next page webpage content, further comprises splicing the pre-read next page webpage page with the current webpage page; and scrolling the page of the current webpage page When the distance exceeds the predetermined threshold, the content of the next page of the pre-reading page is displayed.
- the splicing the pre-read page of the next page with the current page of the webpage includes: extracting only the page of the next page from the pre-read page of the next page BODY node; changes the extracted BODY node into a DIV node but retains the content of the BODY node; sets the attribute of the DIV node to be the tail of the BODY node attached to the current web page after being hidden.
- a webpage browsing method based on a WebApp framework comprising: after receiving a fourth message sent by a browser to invoke a fourth JS application pre-registered in a WebApp framework, the WebApp invokes The fourth JS application performs the determination of the pre-read keywords and the web content pre-reading and display process based on the determined pre-read keywords.
- the determining of the pre-reading keyword and the web content pre-reading and displaying process based on the determined pre-reading keyword may include: traversing the DOM tree to obtain keywords included in the DOM node text; based on the DOM node text The keyword contained in the keyword and the pre-stored keyword database in the WebApp framework to determine whether the keyword is a pre-read keyword; after determining that the included keyword is a pre-read keyword, for each pre-read keyword Repeat the following process until all the pre-read keywords have been processed: According to the currently acquired pre-read keywords, obtain the link address of the next page page; according to the obtained link address, pre-read the next page from the web server Contenting; and displaying the content of the next page of the pre-reading page and obtaining the next pre-reading keyword, wherein the fourth message is sent after completing the construction of the DOM tree of the current webpage page, and the fourth JS application is set to be
- the DOM tree is called after the build is completed and is formed by Content Script, and is pre-programmed
- the operations of the second JS application, the third JS application, and/or the fourth JS application are performed using an extended JS interface.
- the extended JS interface is further configured to: adopt an interface for adjusting a page layout manner according to the extracted content. Set the layout of your browser.
- an apparatus for executing JavaScript by using an extended JS interface includes: an interrogation unit, configured to, when a webpage page loads, ask a requester whether to execute extended JavaScript at a predetermined timing, wherein The extension program is loaded when the browser is launched; an assembly unit for assembling the extended JS interface according to the open API when determining the JavaScript that needs to execute the extension; and an execution unit for performing the extension using the extended JS interface JavaScrip
- a WebApp framework including: a first calling module, configured to receive a first pre-registration in a WebApp framework upon receiving an instruction issued by a browser After the first message of the JS application, the first JS application is called to determine whether the current webpage page is a customizable forum page, and the first JS application is set to be called after the HEAD node is completed and used to determine the current webpage page.
- the first message is sent after the HEAD node of the current webpage is completed when the webpage is loaded to the browser;
- the second calling module is configured to determine that the current webpage is a customizable forum page and receives the browser
- the second JS application corresponding to the forum type of the current webpage page is invoked to generate and display the customized forum page
- the second The JS application is set to be called after the DOM tree is built and used to generate and display the forum page, the second message being issued after the DOM tree of the current web page is completed when the web page is loaded to the browser.
- the WebApp framework may further include: a third calling module, configured to: in response to the indication issued by the browser, invoke a third message of the third JS application pre-registered in the WebApp framework Thereafter, the third JS application is invoked to perform the determination of the pre-read keywords and the web content pre-reading and display process based on the determined pre-read keywords.
- a third calling module configured to: in response to the indication issued by the browser, invoke a third message of the third JS application pre-registered in the WebApp framework Thereafter, the third JS application is invoked to perform the determination of the pre-read keywords and the web content pre-reading and display process based on the determined pre-read keywords.
- the determining of the pre-reading keyword and the web content pre-reading and displaying process based on the determined pre-reading keyword may include: traversing the DOM tree to obtain keywords included in the DOM node text; based on the DOM node text The keyword contained in the keyword and the pre-stored keyword database in the WebApp framework to determine whether the keyword is a pre-read keyword; after determining that the included keyword is a pre-read keyword, for each pre-read keyword Repeat the following process until all the pre-read keywords have been processed: According to the currently acquired pre-read keywords, obtain the link address of the next page page; according to the obtained link address, pre-read the next page from the web server Contenting; and displaying the content of the next page of the pre-reading page and obtaining the next pre-reading keyword, wherein the third message is sent after completing the construction of the DOM tree of the current webpage page, and the third JS application is set to be The DOM tree is called after the build is completed and is formed by Content Script, and is pre-programmed
- a browser including: a first message sending unit, configured to: after completing the construction of the HEAD node of the current webpage page when loading the webpage, issue an instruction to invoke pre-registration in the WebApp framework
- the first message of the first JS application the first JS application is set to be called after the HEAD node is completed and used to determine the forum type of the current web page
- the second message sending unit is configured to be loaded Complete the DOM of the current web page when the webpage After the tree is constructed, issuing a second message indicating that the second JS application corresponding to the forum type of the current webpage page pre-registered in the WebApp framework is invoked, the second JS application is set to be called after the DOM tree is constructed and Used to generate and display forum pages.
- a WebApp framework including: a fourth calling module, configured to: after receiving an instruction issued by a browser, invoke a fourth message of a fourth JS application pre-registered in the WebApp framework, The fourth JS application is invoked to perform the determination of the pre-read keywords and the web content pre-reading and display process based on the determined pre-read keywords.
- the determining of the pre-reading keyword and the web content pre-reading and displaying process based on the determined pre-reading keyword may include: traversing the DOM tree to obtain keywords included in the DOM node text; based on the DOM node text The keyword contained in the keyword and the pre-stored keyword database in the WebApp framework to determine whether the keyword is a pre-read keyword; after determining that the included keyword is a pre-read keyword, for each pre-read keyword Repeat the following process until all the pre-read keywords have been processed: According to the currently acquired pre-read keywords, obtain the link address of the next page page; according to the obtained link address, pre-read the next page from the web server Contenting; and displaying the content of the next page of the pre-reading page and obtaining the next pre-reading keyword, wherein the fourth message is sent after completing the construction of the DOM tree of the current webpage page, and the fourth JS application is set to be
- the DOM tree is called after the build is completed and is formed by Content Script, and is pre-programmed
- the operations of the second JS application, the third JS application, and/or the fourth JS application are performed using an extended JS interface, and when the current webpage content display is performed,
- the extended JS interface is further configured to: set a browser typesetting manner according to the extracted content, through an interface preset for adjusting a page layout manner.
- a browser including: a fourth message sending unit, configured to: when the web page is loaded, complete the construction of the DOM tree of the current webpage page, issue an instruction to call pre-registration in the WebApp framework A fourth message of the fourth JS application, the fourth JS application being configured to perform the determination of the pre-read keyword and the web content pre-reading and display process based on the determined pre-read keyword.
- the determining of the pre-reading keyword and the web content pre-reading and displaying process based on the determined pre-reading keyword may include: traversing the DOM tree to obtain keywords included in the DOM node text; based on the DOM node text The keywords contained in the keyword and the pre-stored keyword database in the WebApp framework to determine whether the keyword is a pre-read keyword; After the included keywords are pre-read keywords, the following process is repeated for each pre-read keyword until all the pre-read keywords have been processed: According to the currently acquired pre-read keywords, the next page is obtained.
- the fourth JS application is set In order to be called after the DOM tree is built and formed by Content Script, and pre-programmed in the WebApp installation package, and when the WebApp installation package is installed on the browser, the fourth JS application is registered in the WebApp framework.
- a mobile terminal including the above WebApp framework; and the above browser.
- a mobile terminal comprising the above apparatus for executing JavaScript through an extended JS interface; and a browser.
- a computer readable medium having program code executable by a processor, when executed, causes the processor to perform the following steps:
- the predetermined timing asks the extension whether to execute the extended JavaScript, which is loaded when the browser is launched; when it is determined that the extended JavaScript is required, the browser assembles the extended JS interface according to the open application programming interface API. Executing extended JavaScript with the extended JS interface.
- a computer readable medium having program code executable by a processor, when executed, causes the processor to perform the steps of: receiving a browser After instructing to invoke the first message pre-registered in the first JS application in the web application webApp framework, the webApp invokes the first JS application to determine whether the current web page is a customizable forum page, and the first JS application is set to be in HEAD After the node is completed, the node type is used to determine the current webpage page, and the first message is sent after the webpage is loaded into the browser, and the HEAD node of the current webpage is completed; and the current webpage is determined to be After customizing the forum page and receiving the instruction issued by the browser to invoke the second message of the second JS application pre-registered in the WebApp framework, the WebApp invokes the second JS application corresponding to the forum type of the current webpage page to generate and display the second JS application.
- the second JS application is set to DOM tree structure in the document object model After the build is completed, it is called and used to generate and display the forum page, and the second message is sent after the DOM tree of the current webpage is completed when the webpage is loaded to the browser.
- a meter having a program code executable by a processor is provided The computer readable medium, when executed, the program code causes the processor to perform the following steps: after receiving the instruction issued by the browser to invoke the fourth message of the fourth JS application pre-registered in the WebApp framework, the WebApp Calling the fourth JS application to perform determination of the pre-read keyword and the web content pre-reading and displaying process based on the determined pre-reading keyword, wherein the fourth message is completed after the DOM tree of the current web page is completed Issuance, the fourth JS application is set to be called after the DOM tree is built and formed by Content Script, and pre-programmed in the WebApp installation package, and when the WebApp installation package is installed on the browser, the fourth JS is The application is registered in the WebApp framework.
- the customization of the forum mode page can be performed when the DOM tree is constructed, without having to start customization after the web page is loaded, thereby reducing the waiting time of the user and thereby improving the user experience.
- the WebApp's automatic content update script can be used to implement automatic update by using the web application's content script content script without the need of a browser server.
- the forum mode and the reading mode are implemented by a WebApp, and it is no longer necessary to change the code of the browser itself, thereby making maintenance simple.
- the user can create a different forum mode or a read mode WebApp as needed, that is, the method according to the present invention is open.
- FIG. 1 is a flow chart showing a webpage browsing method based on a WebApp framework according to a first embodiment of the present invention
- FIG. 2 illustrates an example process of calling the first JS application determination forum type in FIG. 1
- FIG. 3 illustrates an example process of invoking the second JS application of FIG. 1 to generate and display a forum page;
- FIG. 4 is a block diagram showing a mobile terminal having a WebApp framework and a browser according to a first embodiment of the present invention
- FIG. 5 is a flow chart showing a webpage browsing method based on a WebApp framework according to a second embodiment of the present invention.
- FIG. 6 shows an example process of invoking a third JS application in FIG. 5 for a read mode operation
- FIG. 7 shows a flow chart of an example stitching process
- Figure 8 is a block diagram showing a mobile terminal having a WebApp framework and a browser in accordance with a second embodiment of the present invention
- FIG. 9 is a flow chart showing a method of executing JavaScript using an extended JS interface according to a third embodiment of the present invention.
- Figure 10 is a flow chart showing a method of executing JavaScript to perform page layout control using the extended JS interface of Figure 9;
- FIG. 11 is a block diagram showing an apparatus for executing JavaScript using an extended JS interface according to a third embodiment of the present invention.
- Figure 12 is a block diagram showing a mobile terminal having means for page layout control using an extended JS interface in accordance with the present invention.
- Fig. 1 is a flow chart showing a WebApp framework-based web browsing method in accordance with a first embodiment of the present invention.
- the first JS application ie, the first JS application file
- the second JS application ie, the second JS
- Application file WebApp installation package.
- the first JS application and the second JS application are files for storing JavaScript scripts, formed by Content Script.
- the first JS application is set to be called after the HEAD node is completed and used to determine the forum type of the current web page.
- the first JS application is configured to obtain a meta tag from the HEAD node; Determine the forum type of the web page based on the acquired meta tag.
- the meta tag here refers to an important code " ⁇ meta>" in the HTML source code of the web page.
- the second JS application is set to be called after the DOM tree is built and used to generate and display a forum page.
- the second JS application is configured to: by traversing the DOM tree, extract forum page data corresponding to the customized forum mode in the current webpage page; generate the forum page by using the extracted forum page data; and display the generated forum page.
- step S110 the created WebApp installation package is installed in a browser on the mobile terminal client.
- step 120 the first JS application and the second JS application are registered in the WebApp framework.
- the WebApp framework is similar to an operating system (OS) on which various applications such as JS applications can be run.
- OS operating system
- the above steps may be performed in advance before the user performs web browsing, or may be performed in real time while the user is browsing the web.
- step S130 the current webpage page that the user desires to browse is loaded from the webpage server to the browser on the client of the mobile terminal.
- the browser issues a first message to the WebApp indicating that the first JS application is called (step S140).
- the first message may be HEAD_END or BODY_START
- the message HEAD-END is used to indicate the end of the HEAD node
- the message BODY_START is used to indicate the start of the BODY node.
- the browser can indicate that the first JS application is invoked by sending a message HEAD_END or BODY_START to the WebApp.
- the timing of sending the first message can be issued when the browser has already built the HEAD node, or when the browser starts building the BODY node or after the BODY node is built.
- the browser loads the webpage, the source code of the webpage is first obtained from the network. When parsing the source code of these web pages, it will resolve to the BODY tag. Once parsed into the BODY tag, an instance of the BODY node is created in the browser code. When the instance is successfully created, the WebApp framework BODY node can be notified that it has been constructed, thereby instructing the WebApp to invoke the first JS application file.
- the WebApp After calling the first JS application file, the WebApp uses the first JS application file called to determine the forum type (step S150).
- the Meta tag in the HEAD node is obtained according to the obtained source code of the current webpage page (step S151), and the forum type of the current webpage page is determined according to the acquired Meta tag (step S153).
- the determined forum type is stored in the WebApp (S155). In another example of the present invention, the determined forum type may not be stored.
- step S160 the WebApp determines whether the forum page is a customizable forum based on the determined forum type. If the forum page is not a customizable forum, then in step S165, the browser continues to load the current web page and displays the loaded web page after the loading is completed.
- the browser continues to load the current web page. And after the browser completes the DOM tree construction, the browser sends a second message indicating that the second JS application is invoked to the WebApp (step S180).
- the second message may be, for example, a DOCUMENT_END message indicating that the document ends.
- the browser constructs a DOM tree in the process of parsing the source code obtained from the network. After parsing all the source code of the web page, a complete DOM tree is constructed. At this point, a second message indicating that the second JS application is invoked can be sent to the WebApp framework.
- the second message can be any form of message, as long as the WebApp receives the message to determine that the second JS application should be invoked.
- the WebApp invokes the second JS application to generate and display the forum page.
- the WebApp extracts forum page data corresponding to the customized forum mode in the current webpage page by traversing the DOM tree (step S191); The forum page data generation forum page (step S193); then the generated forum page is displayed (step S195).
- the original web page may also be hidden or deleted before the generated forum page is displayed.
- the method of hiding the original webpage page is to set the CSS (Cascading Style Sheet) attribute of the node of the original webpage page, and the original webpage page can be hidden by setting the CSS property. Effect.
- the method of deleting the original webpage page is to delete the webpage node by calling the interface removeChild provided by JS.
- Fig. 4 shows a block schematic diagram of a mobile terminal 10 having a WebApp framework and browser in accordance with a first embodiment of the present invention.
- the mobile terminal 10 includes a WebApp framework 100 and a browser 200.
- the WebApp framework 100 also includes a first invocation module 110 and a second invocation module 120.
- the first calling module 110 is configured to, after receiving the instruction issued by the browser, invoke the first message pre-registered in the first JS application in the WebApp framework, and invoke the first JS application to determine whether the current webpage page is a customizable forum page.
- the first JS application is set to be called after the HEAD node is completed and used to determine the forum type of the current webpage page, and the first message is completed after the HEAD node of the current webpage page is completed when the webpage is loaded into the browser. issue.
- the second invoking module 120 is configured to: after determining that the current webpage page is a customizable forum page and receiving an instruction issued by the browser, calling the second message of the second JS application pre-registered in the WebApp framework, using the current webpage page a second JS application corresponding to the forum type to generate and display the customized forum page, the second JS application is set to be called after the DOM tree is constructed and used to generate and display the forum page, the second message is Issued after the DOM tree of the current web page is built when the web page is loaded to the browser.
- the browser 200 further includes a first message transmitting unit 210 and a second message transmitting unit 220.
- the first message sending unit 210 is configured to, after completing the construction of the HEAD node of the current webpage page when loading the webpage, issue a first message indicating that the first JS application pre-registered in the WebApp framework is invoked, the first JS application is Set to the type of forum that is called after the HEAD node is built and used to determine the current page page.
- the second message sending unit 220 is configured to, after completing the construction of the DOM tree of the current webpage page when loading the webpage, issue a second second JS application corresponding to the forum type corresponding to the current webpage page, which is pre-registered in the WebApp framework.
- the message, the second JS application is set to be called after the DOM tree is built and used to generate and display the forum page.
- FIGS. 1 through 4 A WebApp framework-based web page browsing method and system according to a first embodiment of the present invention is described above with reference to FIGS. 1 through 4.
- the terminal client opens the forum page, it uses WebApp's Content Script to automatically identify the type of the forum, and calls different JS codes to customize the page according to the type of the forum, and finally generates a clean and refreshing forum mode page instead of the original complicated forum page.
- the browser can run a forum-style WebApp similar to the operating system. In this way, a set of WebApp frameworks can be implemented in the local browser client without the need for server running support, and the forum page forum mode can be customized through Content Script, so that the client browser does not run. Depends on the browser vendor's server.
- the customization of the forum mode page can be performed when the DOM tree is constructed, rather than starting at the end of the page loading.
- the maintenance method is simple, the forum mode can be implemented by a Webapp, and it is no longer necessary to change the browser's own code.
- the method according to the present embodiment is open, and the user can create a Web app for some special forum modes.
- Fig. 5 is a flow chart showing a WebApp framework based web browsing method in accordance with a second embodiment of the present invention.
- the third JS application is a file for storing JavaScript scripts, formed by Content Script.
- the third JS application is configured to be invoked after the DOM tree is constructed and configured to perform the determination of the pre-read keywords and the web content pre-reading and display process based on the determined pre-read keywords.
- FIG. 5 In the example shown in FIG.
- the determination of the pre-reading keyword and the web content pre-reading and displaying process based on the determined pre-reading keyword include: the WebApp traversing the DOM tree to obtain keywords included in the DOM node text Determining whether the keyword is a pre-read keyword based on a keyword included in the DOM node text and a pre-stored keyword database containing the predicted keyword in the WebApp framework; determining that the included keyword is a pre-read key After the word, the following process is repeated for each pre-read keyword until all the pre-read keywords have been processed: According to the currently obtained pre-read keyword, the link address of the next page page is obtained; according to the obtained link The address, pre-reading the content of the next page from the web server; and displaying the content of the next page of the pre-read and obtaining the next pre-read keyword.
- Pre-read keywords that are pre-stored in the keyword database in the WebApp can be collected by observing a large number of websites.
- the pre-read keywords are, for example, "next page”, “next chapter”, “next section”, and the like.
- the keyword database is stored in the configuration file of the WebApp, and when the WebApp is started, all the pre-read keywords saved in the configuration are read.
- the WebApp installation package is created as described above, before web browsing or web browsing, the WebApp installation package is installed in the browser in step S210. After the above installation is completed, the third JS application is registered in the WebApp in step S220.
- step S230 the current webpage page that the user desires to browse is loaded from the webpage server to the browser on the client of the mobile terminal.
- the browser issues a third message to the WebApp indicating that the third JS application is called (step S240).
- the third message can adopt any form of message, as long as the WebApp can confirm that the third JS application should be called after receiving the message.
- step S250 the WebApp invokes the third JS application to perform the read mode operation.
- the WebApp traverses the DOM tree to acquire the keywords included in the text of the DOM node (S251). Then, the acquired keyword is matched with the pre-read keyword pre-stored in the configuration of the WebApp, and it is judged whether or not the keyword is a pre-read keyword (S252). If so, it is determined that the reading mode is entered, and the process proceeds to step S253. Otherwise, it is judged that the reading mode is not entered, and the process proceeds to step S257. In step S257, the loading of the page continues to be displayed.
- JS provides a way to traverse the DOM tree.
- the innerText property of a node you can get the display text of this node.
- the string matching method provided by JS is used to compare the pre-read keyword previously saved in the configuration with the content of the node, if a pre-read is found in the set of pre-read keywords.
- the keyword whose content is the same as the content of the text, considers that the current page can enter the reading mode.
- the following process is repeatedly executed for each pre-reading keyword until all the pre-reading keywords have been processed:
- the page address of the page page (S253), for example, through Javascript DOM Do, get the text of the next page link address.
- the next page content is pre-read from the web server (S254), for example, based on the link address, a request is sent to the web server to obtain the web page content.
- next page webpage page is spliced with the current webpage page (S255); and when the page scrolling distance of the current webpage page exceeds a predetermined threshold, the pre-read next page webpage content is displayed and the next pre-reading keyword is acquired (S256).
- the next page page may not be spliced with the current page page, and the next page page is displayed after the current page has been browsed.
- steps S253 to S256 are repeated until the above operation is completed for all the pre-read keywords.
- splicing the pre-read next page page with the current web page may further include: extracting only the next page from the pre-read next page page. a BODY node of the web page (S2551); changing the extracted BODY node to a DIV node but retaining the content of the BODY node (S2553); and setting the attribute of the DIV node to a BODY node attached to the current web page after being hidden The tail (S2555).
- Fig. 8 is a block diagram showing a mobile terminal 20 having a WebApp framework and a browser in accordance with a second embodiment of the present invention. As shown in FIG. 8, the mobile terminal 20 includes a WebApp framework 300 and a browser 400.
- the WebApp framework 300 includes a third invoking module 310, configured to invoke a third JS application after receiving a third message sent by the browser to invoke a third JS application pre-registered in the WebApp framework, the third JS application Is configured to perform the following process: traversing the DOM tree to obtain keywords contained in the DOM node text; determining whether the keyword is pre-based based on keywords included in the DOM node text and a pre-stored keyword database in the WebApp framework Read the keyword; after determining that the included keyword is a pre-read keyword, repeat the following process for each pre-read keyword until all the pre-read keywords have been processed: According to the currently acquired pre-read key a word, obtaining a link address of a page of the next page; pre-reading the content of the next page from the web server according to the obtained link address; and displaying the content of the next page of the pre-read and obtaining the next pre-read keyword, wherein The third message is issued after completing the construction of the DOM tree of the current webpage
- the browser 400 includes a third message sending unit 410, configured to, after completing the construction of the DOM tree of the current webpage page when the webpage is loaded, issue a third message indicating that the third JS application pre-registered in the WebApp framework is invoked,
- the third JS application is configured to perform the following process: traversing the DOM tree to obtain keywords contained in the DOM node text; determining the key based on keywords included in the DOM node text and a pre-stored keyword database in the WebApp framework Whether the word is a pre-read keyword; after determining that the included keyword is a pre-read keyword, the following process is repeated for each pre-read keyword until all the pre-read keywords have been processed: according to the current acquisition a pre-reading keyword, obtaining a link address of a page page of the next page; pre-reading the content of the next page from the web server according to the obtained link address; and displaying the content of the next page of the pre-read and obtaining the next pre-read keyword,
- FIGS. 5 through 8 A WebApp-based web browsing method and system according to a second embodiment of the present invention is described above with reference to FIGS. 5 through 8.
- the read mode and the pre-reading of the reading mode can be performed for the page that can enter the reading mode by using the content script of the WebApp without the cooperation of the browser server.
- WebApp's automatic update strategy can be used to update the reading mode implementation in the background, resulting in more timely and less traffic.
- maintenance is simple, and the reading mode can be implemented through a WebApp, eliminating the need to change the browser's own code.
- it is open, and users can create WebApps with different reading modes as needed.
- the first embodiment and the second embodiment of the present invention can be combined to form a new embodiment.
- the third JS application in the second embodiment of the present invention is combined with the first JS application and the second JS application of the first embodiment, and the third embodiment of the second embodiment is added to the WebApp of the first embodiment.
- the second JS application and the third JS application may be executed simultaneously or sequentially.
- the third calling module, the third JS application, the third message sending module, and the third message mentioned in the WebApp framework according to the second embodiment respectively correspond to the claims in claim 4 and claim 12.
- Four calling module, fourth JS application, fourth messaging module, and fourth Message When the second embodiment is used in combination with the first embodiment, the third calling module, the third JS application, the third message transmitting module, and the third message mentioned in the WebApp framework according to the second embodiment respectively correspond to the claims 9 and the third calling module, the third JS application, the third message sending module, and the third message in claim 18.
- FIG. 9 shows a flow chart of a method of executing JavaScript using an extended JS interface in accordance with a third embodiment of the present invention.
- step S310 when the browser is started, the browser extension is loaded (step S310). Then, during the browser browsing process, the web page required by the client is loaded from the web server to the browser (step S320). Next, when the web page is loaded, the browser asks the extension at the predetermined timing whether to execute the extended JavaScript (step S330), for example, before the DOM tree starts to be created or after the DOM tree is created.
- the browser When it is determined that JavaScript is required to execute the extension, the browser assembles the extended JS interface according to the open API (step S340). After the extended JS interface is assembled, the extended JavaScript is executed using the extended JS interface (step S350) to execute various applications according to user needs.
- Figure 10 is a flow chart showing a method of executing JavaScript to perform page layout control using the extended JS interface of Figure 9.
- Steps S310 to S350 in Fig. 10 are identical to steps S310 to S350 in Fig. 9, and the description will not be repeated here.
- step S360 the desired content is browsed by accessing the DOM tree of the current webpage page.
- the layout mode of the browser (S370) is set by an interface for adjusting the page layout mode, for example, by ucweb.tabs.setLayout (layout).
- step S375 the page structure of the web page content from the web server is modified, for example, to mask unnecessary elements and generate specific elements.
- the browser is requested to change the layout mode of the current page according to the set layout mode (S380), whereby the browser re-types according to the set layout mode (S390).
- This interface is used to dynamically change the layout of the page.
- the typesetting method can be zoom typesetting or screen typesetting.
- Input parameters The constant value that identifies the typesetting method, ie ucweb.tabs.ZOOM_LAYOUT Scale layout, ucweb.tabs.ADAPT_SCREEN_LAYOUT indicates suitable screen layout. Return value: None
- the first example is for the case of the extension of the forum mode.
- the page when zooming the layout, the page is found to be able to enter the forum mode.
- the JavaScript of the forum mode extension extracts the content that the forum mode needs to display from the original page, and after shielding unnecessary content, it is displayed to the user in a layout suitable for the screen.
- the forum mode extension program can set the mobile phone browser's typesetting mode to adapt to the screen by calling the ucweb.tabs.setLayout(ucweb.tabs.ADAPT_SCREEN_LAYOUT) interface, thereby providing the user with a beautiful and easy interactive browsing.
- the ucweb.tabs.setLayout(ucweb.tabs.ADAPT_SCREEN_LAYOUT) interface thereby providing the user with a beautiful and easy interactive browsing.
- the second example is for a read mode extension.
- the user enters the reading mode under the zoom layout, and the extension also requests the browser to set the browser to accommodate the screen layout. If the user finds that they do not like the reading mode experience after entering, the user will exit the reading mode.
- the extension program must restore the layout type to the previous zoom layout, and then call the ucweb.tabs.setLayout(ucweb.tabs.ZOOM_LAYOUT) interface to set the layout to zoom layout.
- the extension automatically switches between different layouts to give the user a better browsing experience.
- a web browsing method for the forum mode according to the first embodiment of the present invention can also be performed, which can be combined by the process shown in FIG. 9 and FIG. The process shown or its variants are implemented.
- a web browsing method for a reading mode according to the second embodiment of the present invention can also be performed, which can be combined by the process shown in FIG. 9 and FIG. The process shown in it or a variant thereof is implemented.
- Figure 11 shows a block schematic diagram of an apparatus 1100 for executing JavaScript using an extended JS interface in accordance with a third embodiment of the present invention.
- the apparatus 1000 includes an interrogation unit 1110, an assembly unit 1120, and an execution unit 1130.
- the query unit 1110 is configured to ask the extension program whether to execute the extended JavaScript at a predetermined timing when the browser performs the loading of the web page, wherein the extension program is loaded when the browser is started.
- the assembly unit 1120 is configured to assemble the extended JS interface according to the open API when it is determined that the JavaScript needs to be extended.
- the extended JavaScript is configured to perform the following process: extracting a page browsing desired content by accessing a DOM tree of a current web page; The extracted content is set by using a preset interface for adjusting the page layout mode; and the extracted content is typeset based on the set layout mode.
- FIG. 12 is a block diagram showing a mobile terminal 30 having a page layout control device for page layout control using an extended JS interface in accordance with the present invention. As shown in FIG. 12, the mobile terminal 30 includes the above-described device 1100 and a browser.
- the extended JS interface can be assembled according to the open API, so that the assembled JS interface is used to execute various JavaScript according to the user's needs, so that the extended JS can be used to obtain more functions of the browser, so that the expansion mode is enabled. More flexible.
- the extended JS interface can solve the problem that the user's browser experience is not good due to different layout methods of the mobile phone browser.
- the extension program can be used to enable the extension program to dynamically change the layout mode of the mobile browser according to the content requirements of the webpage, thereby satisfying the different typesetting methods used by different webpages, thereby improving the browsing of the user. Experience.
- the mobile terminal of the present invention can be a variety of handheld terminal devices, such as mobile phones, personal digital assistants (PDAs), etc., and thus the scope of protection of the present invention should not be limited to a particular type of mobile terminal.
- PDAs personal digital assistants
- modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
- they may be implemented by program code executable by a computing device such that they may be stored in a storage device for execution by a computing device, which may be a processor such as a CPU.
- the computing device is configured in a handheld mobile terminal such as a cell phone, PDA, tablet or the like.
- the steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof may be fabricated into a single integrated circuit. Module to achieve.
- non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash.
- ROM read only memory
- PROM programmable ROM
- EPROM electrically programmable ROM
- EEPROM electrically erasable programmable ROM
- flash flash.
- Volatile memory can include random access memory (RAM), which can act as external cache memory.
- RAM can be obtained in a variety of forms, such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM) and direct Rambus RAM (DRRAM) o storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
- DRAM synchronous RAM
- DRAM dynamic RAM
- SDRAM synchronous DRAM
- DDR SDRAM double data rate SDRAM
- ESDRAM enhanced SDRAM
- SLDRAM Synchronous Link DRAM
- DRRAM direct Rambus RAM
- DSP digital signal processor
- ASIC dedicated An integrated circuit
- FPGA field programmable gate array
- a general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller or state machine.
- the processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
- a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
- An exemplary storage medium is coupled to the processor, such that the processor can read information from or write information to the storage medium.
- the storage medium can be integrated with a processor.
- the processor and the storage medium can reside in an ASIC.
- the ASIC can reside in the user terminal.
- the processor and the storage medium may reside as a discrete component in the user terminal.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/368,753 US10185704B2 (en) | 2012-04-28 | 2013-04-27 | Webpage browsing method, webapp framework, method and device for executing javascript and mobile terminal |
RU2014126210/08A RU2604326C2 (ru) | 2012-04-28 | 2013-04-27 | Метод просмотра web-страниц, платформа webapp, метод и устройство для исполнения javascript для мобильных терминалов |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210132741.6 | 2012-04-28 | ||
CN201210132741.6A CN102693280B (zh) | 2012-04-28 | 2012-04-28 | 网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013159745A1 true WO2013159745A1 (zh) | 2013-10-31 |
Family
ID=46858714
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/074887 WO2013159745A1 (zh) | 2012-04-28 | 2013-04-27 | 网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10185704B2 (zh) |
CN (1) | CN102693280B (zh) |
RU (1) | RU2604326C2 (zh) |
WO (1) | WO2013159745A1 (zh) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104580378A (zh) * | 2014-12-12 | 2015-04-29 | 百度在线网络技术(北京)有限公司 | 安装包的处理方法及装置 |
US20150286623A1 (en) * | 2014-04-02 | 2015-10-08 | Samsung Electronics Co., Ltd. | Method and apparatus for marking relevant updates to html 5 |
CN111800492A (zh) * | 2020-06-22 | 2020-10-20 | 深圳壹账通智能科技有限公司 | web网页中文字的标记方法、装置、计算机设备及存储介质 |
CN112579958A (zh) * | 2020-12-23 | 2021-03-30 | 平安银行股份有限公司 | 网页转换方法、装置、计算机设备及可读存储介质 |
Families Citing this family (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102693280B (zh) * | 2012-04-28 | 2014-08-13 | 广州市动景计算机科技有限公司 | 网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 |
WO2014058146A1 (ko) | 2012-10-10 | 2014-04-17 | 에스케이플래닛 주식회사 | 웹 문서의 고속 웹 스크롤을 지원하는 사용자 단말 장치 및 스크롤 방법 |
CN104035753B (zh) * | 2013-03-04 | 2018-11-02 | 优视科技有限公司 | 一种双WebView展示定制页面的方法及系统 |
CN104283920A (zh) * | 2013-07-05 | 2015-01-14 | 腾讯科技(深圳)有限公司 | 一种网络应用路由的方法、服务器、终端和系统 |
CN104573412B (zh) * | 2013-10-16 | 2019-04-23 | 航天信息软件技术有限公司 | 防止拷贝网页文字内容的方法和装置 |
US9934207B1 (en) * | 2014-05-02 | 2018-04-03 | Tribune Publishing Company, Llc | Online information system with continuous scrolling and previous section removal |
CN105094786B (zh) * | 2014-05-21 | 2019-05-28 | 广州市动景计算机科技有限公司 | 基于JavaScript定制页面的方法及系统 |
CN104021003A (zh) * | 2014-06-24 | 2014-09-03 | 歌尔声学股份有限公司 | 修改信息管理系统首页的方法及装置 |
CN105335139B (zh) * | 2014-07-24 | 2019-05-17 | 广州市动景计算机科技有限公司 | 网页显示方法和装置 |
CN105446709B (zh) * | 2014-07-29 | 2019-06-21 | 阿里巴巴集团控股有限公司 | 一种Java应用处理方法及装置 |
CN104239441A (zh) * | 2014-09-01 | 2014-12-24 | 可牛网络技术(北京)有限公司 | 网页加载控制方法和装置 |
CN105630524B (zh) * | 2014-10-31 | 2019-04-12 | 广州市动景计算机科技有限公司 | 网页文本解析方法、装置和移动终端 |
CN106155656B (zh) * | 2015-04-07 | 2021-05-11 | 腾讯科技(深圳)有限公司 | 互联网页面组件调用的方法和装置 |
RU2015115352A (ru) * | 2015-04-24 | 2016-11-20 | Закрытое акционерное общество "Лаборатория Касперского" | Способ запуска браузера в защищенном режиме |
CN105069060B (zh) * | 2015-07-28 | 2020-02-07 | 北京京东尚科信息技术有限公司 | 一种html文档分页排版方法 |
CN106354873B (zh) * | 2015-09-22 | 2019-12-20 | 广州神马移动信息科技有限公司 | 网页加载方法、装置及系统 |
CN105786511B (zh) * | 2016-02-29 | 2019-05-07 | 四川长虹电器股份有限公司 | 终端设备Web应用管理的实现方法 |
CN105956026B (zh) * | 2016-04-22 | 2019-08-02 | 北京小米移动软件有限公司 | 网页渲染方法及装置 |
CN106203144A (zh) * | 2016-07-25 | 2016-12-07 | 飞天诚信科技股份有限公司 | 一种实现浏览器访问智能密钥设备的方法及系统 |
GB2568323A (en) * | 2017-03-03 | 2019-05-15 | Google Llc | Systems and methods for detecting improper implementation of presentation of content items by applications executing on client devices |
CN109388766B (zh) * | 2017-08-07 | 2022-07-08 | 阿里巴巴集团控股有限公司 | 页面加载的方法和装置 |
CN110020292B (zh) * | 2017-10-13 | 2020-07-28 | 华为技术有限公司 | 网页内容提取方法以及终端设备 |
CN110895592B (zh) * | 2018-08-22 | 2023-03-17 | 北京字节跳动网络技术有限公司 | 移动终端上的链接启动方法、装置、设备及介质 |
CN110875839B (zh) * | 2018-09-03 | 2022-04-19 | 中国电信股份有限公司 | 网络模型动态扩展方法和系统、计算机可读存储介质 |
CN109358973B (zh) * | 2018-09-29 | 2020-12-22 | 网易(杭州)网络有限公司 | 信息处理方法、系统、介质和计算设备 |
CN110324410B (zh) * | 2019-06-18 | 2022-04-05 | 中国南方电网有限责任公司 | 发起网页请求的方法、装置、计算机设备和存储介质 |
CN110381118B (zh) * | 2019-06-19 | 2022-03-04 | 平安普惠企业管理有限公司 | 页面数据传输的控制方法和相关设备 |
CN111695064B (zh) * | 2020-04-29 | 2023-08-18 | 北京城市网邻信息技术有限公司 | 一种埋点加载方法及装置 |
CN112199097B (zh) * | 2020-10-13 | 2024-01-05 | 深圳市广和通无线股份有限公司 | 安装包生成方法、装置、计算机设备和存储介质 |
CN112559121A (zh) * | 2020-10-20 | 2021-03-26 | 四川天邑康和通信股份有限公司 | 一种IPTV浏览器JavaScript扩展对象的处理方法和系统 |
CN112364269B (zh) * | 2020-11-24 | 2023-08-22 | 中国电子科技集团公司第十五研究所 | 一种基于URL创建WebApp图形应用的方法 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070256003A1 (en) * | 2006-04-24 | 2007-11-01 | Seth Wagoner | Platform for the interactive contextual augmentation of the web |
CN101876897A (zh) * | 2009-04-30 | 2010-11-03 | 国际商业机器公司 | 用于在Web浏览器上处理Widget的系统和方法 |
CN102073502A (zh) * | 2011-01-11 | 2011-05-25 | 百度在线网络技术(北京)有限公司 | 一种利用web原生布局进行页面渲染的方法及装置 |
CN102214098A (zh) * | 2011-06-15 | 2011-10-12 | 中山大学 | 一种基于WebKit浏览器引擎的动态页面数据采集方法 |
CN102693280A (zh) * | 2012-04-28 | 2012-09-26 | 广州市动景计算机科技有限公司 | 网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6311180B1 (en) * | 2000-03-28 | 2001-10-30 | Linx Data Terminals, Inc. | Method for mapping and formatting information for a display device |
EP1977313B1 (en) * | 2006-01-23 | 2018-05-23 | Nokia Technologies Oy | End-to-end solution for an end-user to obtain desired information in user interfaces |
RU2326433C1 (ru) * | 2007-05-14 | 2008-06-10 | Владимир Владимирович Никитенко | Способ упрощения доступа к интернет-ресурсам, размещенным в сети интернет, ссылки на которые публикуются в печатных и электронных изданиях |
CN101325602A (zh) * | 2008-07-30 | 2008-12-17 | 广州市动景计算机科技有限公司 | 一种微浏览器智能预读网页的方法及系统 |
RU2447506C2 (ru) * | 2008-09-03 | 2012-04-10 | Елена Валерьевна Папченко | Способ повышения популярности творческих проектов и компьютерный сервер для его реализации |
US8869256B2 (en) * | 2008-10-21 | 2014-10-21 | Yahoo! Inc. | Network aggregator |
CN101645084A (zh) * | 2009-04-23 | 2010-02-10 | 中国科学院声学研究所 | 一种嵌入式浏览器对动态数据的处理方法 |
US20100293448A1 (en) * | 2009-05-15 | 2010-11-18 | Infonow Corporation | Centralized website local content customization |
CN101571876B (zh) * | 2009-05-26 | 2011-12-07 | 华为技术有限公司 | 脚本程序运行逻辑扩展的方法、服务器和客户端 |
US8522132B2 (en) * | 2010-09-13 | 2013-08-27 | International Business Machines Corporation | Widget behavior customization via cascaded style sheets |
US20120110433A1 (en) * | 2010-10-28 | 2012-05-03 | Microsoft Corporation | Parallel web page processing |
CN102346770B (zh) * | 2011-09-21 | 2014-05-14 | 晨星软件研发(深圳)有限公司 | WebKit浏览器网页内容加载方法及装置 |
US8627204B2 (en) * | 2011-10-18 | 2014-01-07 | Microsoft Corporation | Custom optimization of web pages |
US8639680B1 (en) * | 2012-05-07 | 2014-01-28 | Google Inc. | Hidden text detection for search result scoring |
CN104035753B (zh) * | 2013-03-04 | 2018-11-02 | 优视科技有限公司 | 一种双WebView展示定制页面的方法及系统 |
US9467434B2 (en) * | 2013-07-15 | 2016-10-11 | Salesforce.Com, Inc. | Document rendering service |
-
2012
- 2012-04-28 CN CN201210132741.6A patent/CN102693280B/zh active Active
-
2013
- 2013-04-27 WO PCT/CN2013/074887 patent/WO2013159745A1/zh active Application Filing
- 2013-04-27 RU RU2014126210/08A patent/RU2604326C2/ru active
- 2013-04-27 US US14/368,753 patent/US10185704B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070256003A1 (en) * | 2006-04-24 | 2007-11-01 | Seth Wagoner | Platform for the interactive contextual augmentation of the web |
CN101876897A (zh) * | 2009-04-30 | 2010-11-03 | 国际商业机器公司 | 用于在Web浏览器上处理Widget的系统和方法 |
CN102073502A (zh) * | 2011-01-11 | 2011-05-25 | 百度在线网络技术(北京)有限公司 | 一种利用web原生布局进行页面渲染的方法及装置 |
CN102214098A (zh) * | 2011-06-15 | 2011-10-12 | 中山大学 | 一种基于WebKit浏览器引擎的动态页面数据采集方法 |
CN102693280A (zh) * | 2012-04-28 | 2012-09-26 | 广州市动景计算机科技有限公司 | 网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150286623A1 (en) * | 2014-04-02 | 2015-10-08 | Samsung Electronics Co., Ltd. | Method and apparatus for marking relevant updates to html 5 |
CN104580378A (zh) * | 2014-12-12 | 2015-04-29 | 百度在线网络技术(北京)有限公司 | 安装包的处理方法及装置 |
CN111800492A (zh) * | 2020-06-22 | 2020-10-20 | 深圳壹账通智能科技有限公司 | web网页中文字的标记方法、装置、计算机设备及存储介质 |
CN112579958A (zh) * | 2020-12-23 | 2021-03-30 | 平安银行股份有限公司 | 网页转换方法、装置、计算机设备及可读存储介质 |
CN112579958B (zh) * | 2020-12-23 | 2024-05-10 | 平安银行股份有限公司 | 网页转换方法、装置、计算机设备及可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US20150074513A1 (en) | 2015-03-12 |
US10185704B2 (en) | 2019-01-22 |
RU2014126210A (ru) | 2016-06-20 |
RU2604326C2 (ru) | 2016-12-10 |
CN102693280A (zh) | 2012-09-26 |
CN102693280B (zh) | 2014-08-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2013159745A1 (zh) | 网页浏览方法、WebApp框架、执行JavaScript方法及装置、移动终端 | |
JP4208081B2 (ja) | 複数のウェブサイトにパーソナライズされた価値を追加するためのシステム、ウェブサーバ、方法およびプログラム | |
US8386955B1 (en) | User-optimized content for web browsing windows | |
US8612418B2 (en) | Mobile web browser for pre-loading web pages | |
US8522132B2 (en) | Widget behavior customization via cascaded style sheets | |
US8799353B2 (en) | Scope-based extensibility for control surfaces | |
CN106716351B (zh) | 显示网页的方法和电子设备 | |
WO2019072201A1 (zh) | 网页内容提取方法以及终端设备 | |
WO2013178094A1 (zh) | 页面显示方法及装置 | |
WO2013149455A1 (zh) | 对网页进行换肤处理的方法和装置以及移动终端 | |
US10084878B2 (en) | Systems and methods for hosted application marketplaces | |
US20140047359A1 (en) | Mechanism for adding new search modes to user agent | |
WO2014134934A1 (zh) | 一种双WebView展示定制页面的方法及系统 | |
US20120323950A1 (en) | Embedded query formulation service | |
US9645707B1 (en) | Alternative view-based navigation | |
WO2018141300A1 (zh) | 网页预读方法、网页访问方法、设备及电子设备 | |
US20150087277A1 (en) | Method and apparatus for calling an extension | |
US20110004602A1 (en) | Method for generating widget icon, apparatus for generating widget summary information file, and widget engine | |
WO2016050124A1 (zh) | 网页转码方法、装置以及服务器 | |
WO2024011899A1 (zh) | 微件的加载方法、装置、设备以及存储介质 | |
KR20120016333A (ko) | 웹 어플리케이션을 위한 사전 캐싱 방법 및 이를 적용한 단말 장치 | |
US9575617B1 (en) | Navigation payload injection | |
CN112905920A (zh) | 一种页面显示的方法和装置 | |
Aryal | Design Principles for Responsive Web | |
CN115062255B (zh) | 网站适配的方法、装置、电子设备及计算机可读存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13781938 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14368753 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2014126210 Country of ref document: RU Kind code of ref document: A |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13781938 Country of ref document: EP Kind code of ref document: A1 |