| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hey guys, saw this (pretty old) issue about page dictionaries and found an existing CPDF_ api for this so I thought about making it public (while also adding a set of tests for public API and a few more things. Let me know if we:
a. Need any documentation/design docs of any kind
b. If there needs to be any discussion on whether to go ahead with the feature.
The page dictionary is likely just a start and after this I'd want to give a shot at some of the other dictionaries.
Thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
reinterpret_cast<FPDF_STRING>(string_ptr->GetString().c_str());This could probably UAF, so need to find a way around it, might consider the buffer/buflen that a lot of other apis use.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
reinterpret_cast<FPDF_STRING>(string_ptr->GetString().c_str());This could probably UAF, so need to find a way around it, might consider the buffer/buflen that a lot of other apis use.
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
return reinterpret_cast<FPDF_DICTIONARY>(dict->GetDictFor(key).Get());CPDFDictFromFPDFDict(). Done.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
return {rect.left, rect.top, rect.right, rect.bottom};Maybe use an out parameter and reserve the return for a success/failure indicator? Same for GetMatrix() below.
(I don't have any experience in the matter, I was just under the impression that most other APIs seem to be designed that way...)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
return {rect.left, rect.top, rect.right, rect.bottom};Maybe use an out parameter and reserve the return for a success/failure indicator? Same for GetMatrix() below.
(I don't have any experience in the matter, I was just under the impression that most other APIs seem to be designed that way...)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Aryan KrishnanMaybe use an out parameter and reserve the return for a success/failure indicator? Same for GetMatrix() below.
(I don't have any experience in the matter, I was just under the impression that most other APIs seem to be designed that way...)
Good point. Thanks for the suggestion - will update.
Should be done now.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
FPDF_DictionaryGetMatrix(FPDF_DICTIONARY dictionary, Realized this needs CL format.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Realized this needs CL format.
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Ping + Let me know about
1. If it is fine for us to go in this direction with a public read-only api?
2. Any design documentation or anything else of the sort needed?
3. If I should split this up (initially did not because if I add to the header then they need c++, which needs tests), although I can have the tests in a separate cl.