CN111814086A - Method and system for screenshot of webpage - Google Patents
Method and system for screenshot of webpage Download PDFInfo
- Publication number
- CN111814086A CN111814086A CN202010670172.5A CN202010670172A CN111814086A CN 111814086 A CN111814086 A CN 111814086A CN 202010670172 A CN202010670172 A CN 202010670172A CN 111814086 A CN111814086 A CN 111814086A
- Authority
- CN
- China
- Prior art keywords
- screenshot
- target
- webpage
- request
- web page
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000005096 rolling process Methods 0.000 claims description 4
- 230000009191 jumping Effects 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims 1
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 239000008186 active pharmaceutical agent Substances 0.000 description 6
- BUGBHKTXTAQXES-UHFFFAOYSA-N Selenium Chemical compound [Se] BUGBHKTXTAQXES-UHFFFAOYSA-N 0.000 description 3
- 229910052711 selenium Inorganic materials 0.000 description 3
- 239000011669 selenium Substances 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- 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/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Abstract
The invention provides a method and a system for screenshot of a webpage, wherein the method comprises the steps of receiving a screenshot request, wherein the screenshot request comprises a target webpage URL and a target element selector; skipping to a target webpage according to the URL of the target webpage; and performing screenshot on the target webpage according to the target element selector to obtain the webpage screenshot.
Description
Technical Field
The invention relates to a screenshot technology, in particular to a method and a system for screenshot of a webpage.
Background
A screenshot is a visual image captured by a computer, cell phone, tablet computer, etc. that can be displayed on a screen or like display device. With the development of the internet, screenshots are increasingly frequently applied to scenes such as social chat, image processing, report analysis and the like. Current screenshots of web pages are typically taken "offline". That is, when screenshot is performed, a target webpage needs to be opened in a browser first, then screenshot is completed by using an "offline screenshot tool", and finally the captured image is stored in a local device. The offline screenshot tools commonly used in the art include screenshot tools integrated in chat software such as QQ, professional screenshot tools such as ScreenFloat, and self-contained screenshot tools in an operating system.
However, when the offline screenshot tool is used, a user needs to manually operate the offline screenshot tool, so that the operation accuracy is not high, and the screenshot efficiency is low.
Disclosure of Invention
One aspect of the invention relates to a method for screenshot of a web page, comprising: receiving a screenshot request, wherein the screenshot request comprises a target web page URL and a target element selector; skipping to a target webpage according to the target webpage URL; and performing screenshot on the target webpage according to the target element selector to obtain a webpage screenshot.
Yet another aspect of the invention relates to a system for screenshot of a web page, comprising: means for receiving a screenshot request, wherein the screenshot request includes a target web page URL and a target element selector; a module for jumping to a target webpage according to the target webpage URL; and the screenshot module is used for screenshot the target webpage according to the target element selector so as to obtain the webpage screenshot.
The webpage screenshot method and the webpage screenshot system can realize automatic screenshot and batch screenshot, not only improve the efficiency, but also realize accurate screenshot of the target image. In addition, in the embodiment of the invention, the intercepted image can be stored on line, so that different users in the Internet can use the screenshot conveniently. Furthermore, the invention also performs special design aiming at different scenes in screenshot operation, thereby improving the applicability and the convenience of users: for example, a "login scenario" and a "lazy loading (rolling loading) scenario" are supported, i.e., simulating a user login and capturing the logged-in web page and allowing custom loading of data and capturing the loaded web page.
Drawings
FIG. 1 is a flow diagram of a web page screenshot method according to one embodiment of the present invention.
Fig. 2 is a flow diagram of the method of step 9 in fig. 1 according to one embodiment of the invention.
FIG. 3 is a schematic diagram of a web page screenshot system according to one embodiment of the present invention.
Fig. 4A-4C are schematic diagrams of a screenshot request and a captured image according to an embodiment of the invention.
Detailed Description
The content of the invention will now be described with reference to a number of exemplary embodiments. It is to be understood that these examples are set forth merely to enable those of ordinary skill in the art to better understand and thereby implement the teachings of the present invention, and are not intended to suggest any limitation as to the scope of the invention.
As used herein, the term "include" and its variants should be read as open-ended terms meaning "including, but not limited to. The term "based on" should be read as "based, at least in part, on. The terms "one embodiment" and "an embodiment" should be read as "at least one embodiment". The term "another embodiment" should be read as "at least one other embodiment".
FIG. 1 illustrates a flow diagram of a web page screenshot method in accordance with one embodiment of the present invention. In embodiments of the present invention, the process may also include one or more additional steps. In embodiments of the present invention, one or more steps in the flow may be omitted or repeated. In the examples of the present invention, the sequence number of a step does not necessarily imply the ordering of the step, for example step 1 may be performed before step 2 in some embodiments, but it may also be performed after step 2 in other real-time schemes. The following is a detailed description of the various steps shown in FIG. 1:
at step 1, a screenshot request is received. As used in embodiments of the present invention, a "screenshot request" may be a screenshot instruction sent by a user. In an embodiment of the invention, the screenshot request includes the URL of the web page on which the screenshot is to be performed and an element selector. As used in embodiments of the present invention, "element" has a meaning conventionally understood by those skilled in the art, and refers to an element defined in HTML language or similar language, or an element having a similar meaning in other contexts. An HTML page is a text file composed of various HTML elements that constitute the basic unit of an HTML page (see definition in Wikipedia, https:// zh. wikipedia. org/wiki/HTML% E5%, 85%, 83% E7%, B4% A0). As used in embodiments of the present invention, an "element selector" (simply "selector") has the meaning conventionally understood by those skilled in the art, and refers to an identifier for specifying an element by which a computer system can locate its specified element. In embodiments of the present invention, the URL, element, and element selector of the web page to which the screenshot is to be implemented may also be referred to as a target URL, a target element, and a target element selector.
In embodiments of the present invention, the screenshot request may also include one or more of a web page jump timeout time, a login timeout time, a return data type, an export file type, a lazy load attribute, and an automatic pull-down scroll time. As used in an embodiment of the present invention, the "web page jump timeout time" refers to a time required for a browser to jump to a web page URL, indicating whether the jump failed. In the embodiment of the present invention, the webpage jump timeout time is usually preset, for example, 5 seconds, and if the browser still does not jump to the target webpage URL within 5 seconds, it is considered that the jump fails and the current screenshot operation is ended. As used in embodiments of the present invention, the "login timeout time" refers to the time required for the browser to complete the login, indicating whether the login failed. In the embodiment of the present invention, the login timeout time is usually preset, for example, 5 seconds, and if the browser still does not log in within 5 seconds, the login is considered to fail and the current screenshot operation is ended. As used in embodiments of the present invention, the "return data type" refers to whether the captured image is returned directly after completion of the screenshot or an ID corresponding to the online stored image (through which the user can access, view, etc. the screenshot). As used in embodiments of the present invention, an "export file type" refers to the file format of a screenshot, including but not limited to JPEG, PNG, and PDF. As used in the embodiment of the present invention, the "lazy loading attribute" is used to indicate whether a target web page can be lazy loaded, where "lazy loading" is also called "rolling loading", which has a meaning conventionally understood by those skilled in the art, and refers to a data acquisition method that can automatically acquire more data when a user rolls a page, and newly acquired data does not affect the display of original data, while resource consumption at a server side is reduced to the maximum extent. As used in embodiments of the present invention, "automatic pull-down scroll time" refers to the maximum time of default pull-down scroll in the case of lazy loading, for example, some web pages support unlimited lazy loading, at which time a time threshold may be preset, for example, 10 seconds, and after 10 seconds is exceeded, lazy loading is not continued.
In an embodiment of the present invention, if the target element is a child element contained within a parent element having a scroll attribute, it is necessary to indicate the selector of the parent element at the same time as indicating the selector of the child element to implement the scroll loading and screenshot. In an embodiment of the present invention, if the target element is a child element contained within a parent element that does not have a scrolling property, only the selector of the child element may be indicated, without indicating the selector of the parent element. In embodiments of the present invention, "having a scroll property" means that a lazy load operation may be performed. As used in embodiments of the present invention, "parent element" and "child element" have meanings conventionally understood by those skilled in the art: the HTML elements that make up an HTML web page are organized as nested structures, with the outer layers being parent elements and the inner layers being child elements.
In embodiments of the present invention, the selector of the target element may be obtained by viewing the HTML code, for example, the selector of the target element may be obtained by a review element function of a Chrome/Chrome browser. In the embodiment of the present invention, the selector of the target element may also be acquired by other methods as long as it can achieve the object of the present invention. In an embodiment of the invention, the screenshot request may be in the JSON data format. In embodiments of the present invention, the screenshot request may also be in other data formats known in the art.
At step 2, the screenshot request is parsed. In embodiments of the present invention, the screenshot request may be parsed using techniques known in the art. In an embodiment of the present invention, the screenshot request may be parsed into an operation instruction capable of calling the API, preferably, an operation instruction conforming to the Puppeteer API known in the art. In embodiments of the invention, the screenshot request may be parsed into other forms of operational instructions.
And at step 3, judging a screenshot scene according to the screenshot request. In embodiments of the present invention, screenshot scenarios include, but are not limited to, login scenarios, lazy load scenarios, and batch screenshot scenarios. In an embodiment of the login scenario of the present invention, the screenshot request further includes an element selector of an account password input box and a corresponding account and password. In embodiments of the lazy load scenario of the present invention, the screenshot request also contains a lazy load attribute and an automatic pull-down scroll time. In embodiments of the batch screenshot scenario of the present invention, the screenshot request includes more than two web page URLs or more than two element selectors.
At step 4, it is determined whether it is a batch screenshot scenario. In the embodiment of the invention, the judgment of whether the batch screenshot scene belongs to depends on whether the screenshot request comprises more than two webpage URLs or more than two element selectors. In the embodiment of the invention, when the scene belongs to the batch screenshot scene, a plurality of webpage URLs and/or a plurality of element selectors are extracted from the screenshot instruction. In an embodiment of the invention, the web page URL or element selector in the screenshot request is in the form of an array when belonging to a batch screenshot scenario. In an embodiment of the present invention, the two parameters, the web page URL and the element selector, are passed in the form of an array.
At step 5, the number of repetitions of the subsequent link including steps 6-9 is set. In the embodiment of the invention, when the scene belongs to the batch screenshot scene, the times of repeating the steps 6-9 correspond to the number of webpage URLs and element selectors in the screenshot command. For example, when there are two web page URLs and two element selectors are specified in each web page URL, the number of repeating steps 6-8 is 2 times (corresponding to the two web page URLs), and the number of repeating steps 9 is 2 × 2 ═ 4 times (corresponding to the two element selectors in each web page URL). In the embodiment of the invention, when the judgment does not belong to the batch screenshot scene, the step 6 is directly carried out without repetition. For another example, when there are two web page URLs and one element selector is specified in each web page URL, the number of repeating steps 6 to 8 is 2 times, and the number of repeating steps 9 is 2 × 1 ═ 2 times. For another example, when there is only one web page URL and 3 element selectors are specified in the web page URL, the steps 6 to 8 are performed (repeated) only 1 time, and the number of times of repeating the step 9 is 1 × 3 — 3 times.
At step 6, a jump is made to the target web page according to the web page URL in the screenshot request. In an embodiment of the present invention, the operation instruction for performing the jump may be "page. In the embodiment of the invention, if the webpage jump overtime time exists in the screenshot request, whether the webpage jumps successfully or not needs to be judged within the preset time, if the webpage jumps successfully, the next step is continued, and if the webpage jumps unsuccessfully, the current screenshot operation is ended.
At step 7, it is determined whether it is a login scenario. In the embodiment of the invention, whether the user belongs to the login scene depends on whether a selector of an account password input box and a corresponding account and a corresponding password are included in the screenshot request. In the embodiment of the invention, when the user is judged to belong to the login scene, the element selector corresponding to the account password and the input box thereof is extracted from the screenshot command.
At step 8, an account password is entered for login. In an embodiment of the present invention, the input of the account password may be simulated on the target webpage, for example, by filling the account password into the corresponding input box through the operation instruction "page. In the embodiment of the present invention, other operation instructions may also be used for login. In the embodiment of the invention, if the screenshot request includes login timeout time, whether login is successful or not needs to be judged within preset time, if the login is successful, the next step is continued, and if the login is failed, the current screenshot operation is ended.
At step 9, screenshot is captured and the screenshot results are returned. In an embodiment of the invention, the screenshot is returned to the user in the form of a file (e.g., a file compression package) or a filename JSON array (file ID) according to the type of data returned in the screenshot request. In an embodiment of the present invention, when the type of the returned data is a file ID, the intercepted image file (JPEG, PNG, or PDF) may be stored on the server, and the file name may be returned to the user. In the embodiment of the batch screenshot scene, a batch of screenshot targets can be obtained from the screenshot command, and each screenshot result is returned. In embodiments of the invention, the same or different return data types may be used for different intercept targets. In embodiments of the invention, different intercept targets may be returned separately or together, for example in the form of compressed packets.
Fig. 2 shows a flow diagram of the method of step 9 in fig. 1 according to an embodiment of the invention. In embodiments of the present invention, the process may also include one or more additional steps. In embodiments of the present invention, one or more steps in the flow may be omitted or repeated. In the examples of the invention, the sequence number of a step does not necessarily imply a ranking of the step, for example step 9.1 may be performed before step 9.2 in some embodiments, but it may also be performed after step 9.2 in other real-time scenarios. The following is a detailed description of the steps shown in fig. 2:
at step 9.1, the screenshot area is determined. In the embodiment of the invention, different methods can be adopted according to the size of the screenshot area. In the embodiment of the invention, the method for intercepting the whole webpage is different from the method for intercepting the custom area. In embodiments of the invention, the custom area is different than the entire web page. In embodiments of the present invention, the entire web page is intercepted without specifying the element selector or the element selector as null. In the embodiment of the present invention, when the custom region is intercepted, the element selector constituting the custom region needs to be specified, that is, the element selector is not empty.
At step 9.2, it is determined whether it is a lazy loading scenario. In the embodiment of the invention, the judgment of whether the scene belongs to the lazy loading scene depends on whether the screenshot request contains lazy loading attributes and automatic pull-down scroll time.
At step 9.3, the page is lazily loaded. In the embodiment of the invention, when the scene is judged to belong to a lazy loading scene, the automatic pull-down rolling time can be extracted from the screenshot instruction. In the embodiment of the invention, the current page is loaded for a preset time according to the automatic pull-down scrolling time in the screenshot instruction. In the embodiment of the invention, when the situation that the page does not belong to the lazy loading scene is judged, lazy loading is not carried out, and screenshot is only carried out on the loaded page.
At step 9.4, the position of the target element is located. In the embodiment of the invention, the position of the target element to be subjected to screenshot in the webpage can be positioned according to the element selector in the screenshot instruction. In embodiments of the present invention, the location of the target element in the web page includes one or more of its distance to the left, right, top, bottom of the window (i.e., the window of the viewable area) and the size (width and height) of the target element, as long as the actual location of the target element can be determined.
At step 9.5 it is determined whether the element is within the visible region. In an embodiment of the present invention, the "visible region" refers to a window of a browser, i.e., a region that a user can see.
At step 9.6, the page is scrolled to move the target element into the viewable area. In an embodiment of the present invention, the purpose of moving the target element to the visible area is to load the target element, and if the target element is already in the visible area but cannot be viewed by the user due to being occluded by other elements, the target element is already loaded, and therefore implementation of the method of the present invention is not affected. In an embodiment of the invention, the method of the invention is implemented on the premise that the target element has been loaded, without requiring the target element to be visible to the user. In an embodiment of the present invention, if the target element is not in the visible region, the page may be scrolled (e.g., an operation instruction to increase page scrolling), and the target element is moved into the visible region. In an embodiment of the invention, the position of the target element may be located again at step 9.4 and a decision made at step 9.5 after scrolling the page.
At step 9.7, the screen shot is captured and the result of the screen shot is returned.
At step 10, a screenshot preview request is received and a preview result is returned. In an embodiment of the present invention, the preview request may include a document ID. In embodiments of the invention, after receiving the filename in the preview request, a file search may be performed and the file data returned for previewing.
FIG. 3 shows a schematic diagram of a web page screenshot system according to one embodiment of the invention. Each of the modules in the system is described in detail below. In embodiments of the invention, the system may also include one or more additional modules. In embodiments of the invention, one or more modules in the system may be omitted. In embodiments of the invention, the same module may be multiple. In embodiments of the present invention, "module" and "device" may be used interchangeably.
In an embodiment of the present invention, the system may be an API that provides web page screenshots, preferably an API designed according to the known Restful specification. In an embodiment of the present invention, a system for web screenshot of the present invention includes the following modules:
a screenshot module: after parameters such as webpage URL, element selector, webpage jump timeout time, login timeout time, returned data type, exported file type and the like are appointed through the screenshot request, an API is called to initiate an HTTP request to the server, and the server executes the screenshot operation and returns the generated screenshot file or screenshot file name.
A file preview module: and initiating an HTTP request to the server through a preview interface to acquire webpage screenshot data.
A file storage module: and the server stores the data generated after each screenshot on the server.
An instruction decoding module: and controlling a Chrome/Chrome browser to finish page rendering and element moving, screenshot and other operations by resolving the requested content through Puppeneer, for example.
4A-4C illustrate a screenshot request and a captured image schematic in accordance with an embodiment of the present invention, wherein FIG. 4A illustrates exemplary screenshot instructions instructing a computer to perform a screenshot operation according to the illustrated requirements; FIG. 4B illustrates exemplary result information returned upon completion of the screenshot instruction of FIG. 4A, indicating that the interception was successful; FIG. 4C illustrates an exemplary screenshot for online viewing, the name of which was obtained from the result information returned in FIG. 4B.
The method, apparatus and system of the embodiments of the present invention may be implemented as a pure software module (for example, a software program written in Java language), as a pure hardware module (for example, a special ASIC chip or FPGA chip) as required, or as a module combining software and hardware (for example, a firmware system storing fixed codes).
In the embodiment of the present invention, it is preferable to use a node. js computer language, a Docker software, and a server configured as (equal to or more than) 8 cores 16G.
In the embodiment of the present invention, preferably, the screenshot function implemented by the open source tool Puppeteer is used. Puppeteer, as used in embodiments of the present invention, is a Node library that provides a high level API to control either Chrome or Chrome via the DevTools protocol. And its License is Apache License 2.0, the rights allowed include the patent License, the puppeter related License describes https:// githu. com/google chrome/puppeter/blob/master/liense.
In an embodiment of the invention, the Puppeteer decoding module may be replaced by Selenium in conjunction with PhantomJS. As used in embodiments of the present invention, Selenium is a toolset for web automation testing, and PhantomJS is a Webkit-based "no interface" browser that loads a web site into memory and executes JavaScript scripts on the page. The purposes of controlling the browser to perform page jump, page scrolling, screenshot and the like can be achieved by matching the Selenium with the PhantomJS. In an embodiment of the present invention, the web frame used by the presence server is Koa. In embodiments of the present invention Koa may be replaced by an Express, Hapi, etc. Web framework.
It will be appreciated by persons skilled in the art that the foregoing description is only exemplary of the invention and is not intended to limit the invention. The present invention may include various modifications and variations. Any modifications and variations within the spirit and scope of the present invention should be included within the scope of the present invention.
Claims (16)
1. A method for screenshot a web page, comprising:
receiving a screenshot request, wherein the screenshot request comprises a target web page URL and a target element selector;
skipping to a target webpage according to the target webpage URL; and
and performing screenshot on the target webpage according to the target element selector to obtain a webpage screenshot.
2. The method of claim 1, further comprising:
and storing the webpage screenshot locally or sending the webpage screenshot to a remote server.
3. The method of claim 1, further comprising:
receiving a preview request, wherein the preview request comprises an identifier indicating the webpage screenshot; and
and returning the webpage screenshot according to the preview request so as to preview.
4. The method of claim 1, wherein the screenshot request further includes a web page jump timeout time, and the method further comprises:
and judging whether the webpage is successfully jumped within the webpage jump timeout time, and carrying out screenshot on the target webpage after the webpage is successfully jumped.
5. The method of claim 1, wherein the screenshot request includes more than two target web page URLs and/or more than two target element selectors, and further comprising:
and repeating the operation of jumping to the target webpage and/or the operation of carrying out screenshot on the target webpage according to the number of the target webpage URLs and/or the number of the target element selectors.
6. The method of claim 1, wherein the screenshot request further includes an element selector of an account password entry box and a corresponding account and password, and further comprising:
and inputting the account and the password in the account password input box for logging in.
7. The method of claim 6, wherein the screenshot request further includes a login timeout time, and the method further comprises:
and judging whether the login is successful within the login timeout time, and performing screenshot on the target webpage after the login is successful.
8. The method of claim 1, wherein when the target element selector is empty, the act of screenshot the target web page comprises screenshot the entirety of the target web page; and is
When the target element selector is not empty, the operation of screenshot on the target webpage comprises screenshot on the target element in the target webpage.
9. The method of claim 8, wherein the screenshot request further includes a lazy-load attribute and an automatic pull-down scroll time when the target element selector is empty, and further comprising:
and carrying out lazy loading on the target webpage within the automatic pull-down rolling time.
10. The method of claim 8, wherein when the target element selector is not empty, the method further comprises:
locating the position of the target element according to the target element selector.
11. The method of claim 10, wherein locating the position of the target element comprises determining whether the target element is within a visible region.
12. The method of claim 11, further comprising:
scrolling the target web page to move the target element into the viewable area.
13. A system for screenshot a web page, comprising:
means for receiving a screenshot request, wherein the screenshot request includes a target web page URL and a target element selector;
a module for jumping to a target webpage according to the target webpage URL; and
and the screenshot module is used for screenshot the target webpage according to the target element selector so as to obtain a webpage screenshot.
14. The system of claim 13, further comprising:
a storage module for storing the webpage screenshot locally or sending the webpage screenshot to a remote server.
15. The system of claim 13, further comprising:
means for receiving a preview request, the preview request including an identification indicating the web screenshot; and
and the preview module is used for returning the webpage screenshot according to the preview request so as to preview.
16. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010670172.5A CN111814086A (en) | 2020-07-13 | 2020-07-13 | Method and system for screenshot of webpage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010670172.5A CN111814086A (en) | 2020-07-13 | 2020-07-13 | Method and system for screenshot of webpage |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111814086A true CN111814086A (en) | 2020-10-23 |
Family
ID=72841769
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010670172.5A Pending CN111814086A (en) | 2020-07-13 | 2020-07-13 | Method and system for screenshot of webpage |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111814086A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948737A (en) * | 2021-03-15 | 2021-06-11 | 亿海蓝（北京）数据技术股份公司 | HTML page screenshot method and system |
| CN112948267A (en) * | 2021-03-31 | 2021-06-11 | 北京房江湖科技有限公司 | Webpage testing method, webpage testing system, storage medium and electronic equipment |
| CN113254817A (en) * | 2021-04-24 | 2021-08-13 | 中电长城网际系统应用广东有限公司 | Method for automatically logging in third-party system to obtain page screenshot |
| CN115438287A (en) * | 2022-11-04 | 2022-12-06 | 平安银行股份有限公司 | Method for generating chart without browser mode, electronic device and readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106406851A (en) * | 2016-08-24 | 2017-02-15 | 北京松鼠山科技有限公司 | Webpage image capture method and system |
| CN106610829A (en) * | 2015-10-26 | 2017-05-03 | 北京国双科技有限公司 | Webpage screenshot method and device |
| CN106610831A (en) * | 2015-10-26 | 2017-05-03 | 北京国双科技有限公司 | Webpage screenshot method and device |
| KR20180101913A (en) * | 2017-03-06 | 2018-09-14 | 주식회사 카카오 | Operating method of web server, screen shot server, web browser and target terminal for sharing digital contents |
| CN111309221A (en) * | 2018-12-12 | 2020-06-19 | 阿里巴巴集团控股有限公司 | Page processing method, device and equipment |
-
2020
- 2020-07-13 CN CN202010670172.5A patent/CN111814086A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106610829A (en) * | 2015-10-26 | 2017-05-03 | 北京国双科技有限公司 | Webpage screenshot method and device |
| CN106610831A (en) * | 2015-10-26 | 2017-05-03 | 北京国双科技有限公司 | Webpage screenshot method and device |
| CN106406851A (en) * | 2016-08-24 | 2017-02-15 | 北京松鼠山科技有限公司 | Webpage image capture method and system |
| KR20180101913A (en) * | 2017-03-06 | 2018-09-14 | 주식회사 카카오 | Operating method of web server, screen shot server, web browser and target terminal for sharing digital contents |
| CN111309221A (en) * | 2018-12-12 | 2020-06-19 | 阿里巴巴集团控股有限公司 | Page processing method, device and equipment |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948737A (en) * | 2021-03-15 | 2021-06-11 | 亿海蓝（北京）数据技术股份公司 | HTML page screenshot method and system |
| CN112948267A (en) * | 2021-03-31 | 2021-06-11 | 北京房江湖科技有限公司 | Webpage testing method, webpage testing system, storage medium and electronic equipment |
| CN113254817A (en) * | 2021-04-24 | 2021-08-13 | 中电长城网际系统应用广东有限公司 | Method for automatically logging in third-party system to obtain page screenshot |
| CN115438287A (en) * | 2022-11-04 | 2022-12-06 | 平安银行股份有限公司 | Method for generating chart without browser mode, electronic device and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111814086A (en) | Method and system for screenshot of webpage | |
| US20200104041A1 (en) | System for capturing and replaying screen gestures | |
| US10324828B2 (en) | Generating annotated screenshots based on automated tests | |
| US8225197B1 (en) | Rendering approximate webpage screenshot client-side | |
| KR101340780B1 (en) | Data sharing system and method | |
| US11194456B1 (en) | Webpage testing tool | |
| US9003423B1 (en) | Dynamic browser compatibility checker | |
| US8640037B2 (en) | Graphical overlay related to data mining and analytics | |
| KR101651524B1 (en) | New tab pages and bookmark toolbars in a browser | |
| US20160085520A1 (en) | Application Creation Method and Apparatus | |
| CN107729475B (en) | Webpage element acquisition method, device, terminal and computer-readable storage medium | |
| US10515142B2 (en) | Method and apparatus for extracting webpage information | |
| WO2015039566A1 (en) | Method and system for facilitating automated web page testing | |
| CN104303181B (en) | The network browsing of camera guiding | |
| US20170337168A1 (en) | System and method for generating and monitoring feedback of a published webpage as implemented on a remote client | |
| WO2022086872A1 (en) | Distributed systems and methods for facilitating website remediation and promoting assistive technologies and detecting compliance issues | |
| US9792267B2 (en) | Simplifying identification of potential non-visibility of user interface components when responsive web pages are rendered by disparate devices | |
| CN110347319B (en) | Method and device for screenshot in application | |
| CN109684576A (en) | Web page resources lazyness loads monitoring method, device, equipment and storage medium | |
| EP4198773A1 (en) | Image processing method and apparatus, and computer readable storage medium | |
| US20170169122A1 (en) | Webpage display method, mobile terminal, intelligent terminal, program and storage medium | |
| CN112597052A (en) | Interface testing method and device and computer readable storage medium | |
| US20160004676A1 (en) | Displaying web pages | |
| US11321524B1 (en) | Systems and methods for testing content developed for access via a network | |
| EP3104279B1 (en) | Testing interactive network systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |